This could go back to the 'best practice' debate. Should people try and limit repitition when they can - yes. As well, these tests are mostly for Windows desktop applications, but I also have tested web apps using this setup as well.
Or do I just need more coding practice and a better overall system of doing things?ĮDIT: The tool I'm using is SilkTest, which is in a proprietary language called 4Test. I don't use more structured ways of coding, such as using more OO-principles or functions.ĭo other coders feel this way when writing test code? Obviously I want to follow DRY and YAGNI principles, but I find that test code (automated test code for GUI testing anyway) can make these principles tough to follow. Instead, I usually copy a big chunk of test code from one section and paste it to another, and make any minor changes I need. I find that when I try to use classes or methods more extensively, tests become more cumbersome to maintain and sometimes outright difficult to write in the first place. The reason for this is that the areas I'm testing tend to be similar enough to need repetition but not quite similar enough to encapsulate code into methods or objects. However, I find that I tend to copy and paste a lot of code within tests. My current job is mostly writing GUI test code for various applications that we work on.
0 kommentar(er)
