This question is locked. New answers and comments are not allowed.
hello everyone,
I'm not sure how to get started.
I would like to be able to generate automated tests that meet the following requirements:
1. be able to target different base urls (XXXtest1, XXXtest2, etc..) retrieved when the test is executed from the command line.
2. Make things modular and resusable.
3. Have input parameters like login username/password set in the command line or config file.
4. be able to specify from the command line (or config file) which tests are to be run .
from what i see of teststudio, the above can't be done unless i make the entire thing a coded test case (which is fine). or am i wrong?
It seems like the best approach and the workflow other are using is to simply start out with a main coded steps project, then simply use teststudio to record -> convert to coded steps, and copy and paste these into my main coded steps project. would this be correct?
I'm not sure how to get started.
I would like to be able to generate automated tests that meet the following requirements:
1. be able to target different base urls (XXXtest1, XXXtest2, etc..) retrieved when the test is executed from the command line.
2. Make things modular and resusable.
3. Have input parameters like login username/password set in the command line or config file.
4. be able to specify from the command line (or config file) which tests are to be run .
from what i see of teststudio, the above can't be done unless i make the entire thing a coded test case (which is fine). or am i wrong?
It seems like the best approach and the workflow other are using is to simply start out with a main coded steps project, then simply use teststudio to record -> convert to coded steps, and copy and paste these into my main coded steps project. would this be correct?