Phase 2 - Starting to use Silktest - Setting test files
After taking the advise from the group, I have taken an opportunity to just check out SilkTest and get a feel for it. Please understand, I am new to automated testing and setting this all up on my own without any help. I now would like to start setting up test. I was wondering if you should setup one large test that includes the smaller test in one file or should I make a directory and have files within. I obviously will need to link these test to run them but have them broken down to be able to update the individual pieces. Could you all please "tell me where to go" from here. Thanks.
Re: Phase 2 - Starting to use Silktest - Setting test files
I agree completely. Creating very large test files, in my experience with Silk, tends to create massive dependencies, which in turn is hell to debug and/or maintain. I inherited an acceptence test from somebody who threw together all sorts of functionality testing into one massive test file, and between all the research it took to find out dependencies and variable assignments etc. I could have re-written a large chunk of it.
Unless you are creating a huge suite of tests (thousands), you really can't go wrong with parring down as far as possible the function of your testcases. Like the above message says, they should do one thing and do it well. This makes it easy on everyone -- the designer, the operator, and the debugger, if they happen to be different people. ;-)