Ranorex Organizing tests, best practices et al
Posted: Tue Jul 27, 2010 6:51 pm
Hello,
I want to know if there are any best practices that Ranorex recommends we follow when creating my automation suites using Ranorex.
* Repositories: Do you recommend I have single repository which has all my objects or should it be more like one repository per test case (or a set of related test cases)
*Recordings: What are the best practices regarding recordings. One recording per test case or Record modules and reuse. By record modules and reuse, I mean -- Record an "Open Application" module, "Login Module" " "Logout module" and reuse them in multiple tests. What is recommended? How do ranorex users typically use these.
*Test Data Management: What do Ranorex users typically use as a data pool. I saw an article which defined the use of fitNesse. Is that the standard? Also how is test data typically organized. If for example I use csv files as my datapool, would it typically be like one csv per test case?
Sequence of steps: I realize this is a vague question. What I mean is: what are the sequence of recommended steps in setting up my test automation suites. I have a list of like 200 manual test cases which we'd like to automate. In my case, are the sequence of steps more like: Create one recording per manual test case> Consolidate and clean up repository by deleting redundant items> Set up test data > Replace hard coded test data from recordings by reading from test data file> Test the test scripts > Launch to production.
I think all these are some important questions that need to be thought about when planning your test suites. I would very much appreciate it if someone could answer them.
Thanks in advance!
I want to know if there are any best practices that Ranorex recommends we follow when creating my automation suites using Ranorex.
* Repositories: Do you recommend I have single repository which has all my objects or should it be more like one repository per test case (or a set of related test cases)
*Recordings: What are the best practices regarding recordings. One recording per test case or Record modules and reuse. By record modules and reuse, I mean -- Record an "Open Application" module, "Login Module" " "Logout module" and reuse them in multiple tests. What is recommended? How do ranorex users typically use these.
*Test Data Management: What do Ranorex users typically use as a data pool. I saw an article which defined the use of fitNesse. Is that the standard? Also how is test data typically organized. If for example I use csv files as my datapool, would it typically be like one csv per test case?
Sequence of steps: I realize this is a vague question. What I mean is: what are the sequence of recommended steps in setting up my test automation suites. I have a list of like 200 manual test cases which we'd like to automate. In my case, are the sequence of steps more like: Create one recording per manual test case> Consolidate and clean up repository by deleting redundant items> Set up test data > Replace hard coded test data from recordings by reading from test data file> Test the test scripts > Launch to production.
I think all these are some important questions that need to be thought about when planning your test suites. I would very much appreciate it if someone could answer them.
Thanks in advance!