hi,
we with evaluation version in ranorex (we already order licenses). we try to work in a shared environment, how we suppose to do that? we work from separates workstations and want to share one database (Test cases, Repository....).
TNX
work with Ranorex in group
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: work with Ranorex in group
Hi tzurielya,
To get a better overview about how you could organize your solutions, I would recommend to take a look at the following blog: Organizing a Test Automation Project with Ranorex Test Suites.
To share solutions I would recommend to use a source control environment, like TFS or SVN: Source Control.
Please do let us know if you need further guidance.
Regards,
Markus
To get a better overview about how you could organize your solutions, I would recommend to take a look at the following blog: Organizing a Test Automation Project with Ranorex Test Suites.
To share solutions I would recommend to use a source control environment, like TFS or SVN: Source Control.
Please do let us know if you need further guidance.
Regards,
Markus
Re: work with Ranorex in group
In addition to what Markus said, you should remember that you are developing software. Ranorex is a .NET development environment and you are building a .NET application that tests your product applications.
You will have to work out how you manage requirements (what are you testing, who is writing the specific tests, etc.), who is hanlding test bugs (bugs with the Ranorex test, NOT bugs in the system-under-test), and how to manage source-code activities like merging and branching. You will need to use a software development process just like the developers who are making your product software. It may be a smaller process, but you will still need to do it, otherwise you will end up with a mess as the test project gets bigger.
You will have to work out how you manage requirements (what are you testing, who is writing the specific tests, etc.), who is hanlding test bugs (bugs with the Ranorex test, NOT bugs in the system-under-test), and how to manage source-code activities like merging and branching. You will need to use a software development process just like the developers who are making your product software. It may be a smaller process, but you will still need to do it, otherwise you will end up with a mess as the test project gets bigger.
Shortcuts usually aren't...