Glossary of terms? Adding suites

Best practices, code snippets for common functionality, examples, and guidelines.
conradb
Posts: 19
Joined: Thu Mar 10, 2016 12:00 pm

Glossary of terms? Adding suites

Post by conradb » Tue Apr 19, 2016 4:50 pm

I'm struggling to line up my understanding of "solution", "test case", "repository" and "project", with the way the Studio UI lays things out and what I expected to see.
1. Is there an article describing the terms used in ranorex speak?
2. I have a single solution and want to add many test suites but use the same repository. This should be intuitive, but when I read the forums it mentions adding a new "project", but the project will have a new empty repo. I Want or expect one solution, one repo that is organised into folders, and then many "scripts" - which I assume is an analogy to "suite" in ranorex terminology.

/a_bit_lost :oops:
pros:Powershell automation guru
cons:UI automation hacker/n00b
Conrad Braam

krstcs
Ranorex Guru
Posts: 2683
Joined: Tue Feb 07, 2012 4:14 pm
Location: Austin, Texas, USA

Re: Glossary of terms? Adding suites

Post by krstcs » Wed Apr 20, 2016 2:54 pm

Each project can have ONE AND ONLY ONE test suite. Think of each project AS a test suite. You can just not use the repository in the extra projects. That's what I do. I have one CORE project that contains all of the common modules and the common repository, then I create new projects for each test suite I need.

**Note that when you create a new project, Ranorex defaults to creating a Ranorex Test Library instead of a Suite, so you need to change it before you finish creating the project.


A test case is just a grouping of modules that loops over each row of data in the associated data connector (if there isn't one it just runs the test case one time).


A test module is a group of actions. Try to keep these as small as possible so they are easier to drag and drop where you want them in the test case.
Shortcuts usually aren't...

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Glossary of terms? Adding suites

Post by Support Team » Wed Apr 20, 2016 2:59 pm

Hi conradb,

Most of these terms, are described in our User Guide. Another source of information would be our Blog or Live Webinars.

For your second intention, you could add a new project to your solution.
AddNewProject.png
AddNewProject.png (31.38 KiB) Viewed 602 times
Furthermore change the repository in the recording of the new project, with the repository of your first project.
ChangeRepository.png
ChangeRepository.png (6.76 KiB) Viewed 602 times
At least just choose if you want to copy or link your repository to the Project. By right-clicking on the repository in the "Project Browser" you can select

It is highly recommended going through the User Guide and watch our Webinars as well.

I hope this information helps you.

Kind Regards,
Matthias
.
Image

conradb
Posts: 19
Joined: Thu Mar 10, 2016 12:00 pm

Re: Glossary of terms? Adding suites

Post by conradb » Wed Apr 20, 2016 5:18 pm

Yeah - sorry, my first post took a while to appear, so now I have 2 posts - but this does explain it.
I had assumed I could start with a project that contains all of my recordings and the repository, and then create a second project and place *all* my test suites in the second project to make managing tests separate from the repository and recordings. The "new-project" dialog wizard presents me with a choice of C# and VB, neither of which make any sense to someone who might have no C# nor need any C# coding ability at all.
I was expecting this UI:
ranorexwizard.png
easy to find "Suite" node
ranorexwizard.png (13.73 KiB) Viewed 598 times
Because a suite and a module were at the same hierarchy level in my own mind :wink:

Being under pressure from a boss to just get some basic stuff working kinda means I ran before I could walk.
Loving the tool, but not loving the deadlines. I've a lot of reading to still do.
pros:Powershell automation guru
cons:UI automation hacker/n00b
Conrad Braam