jose_pjoseph
Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Execute tests in a single project on 2 slaves
Consider a project with 100 tests which has a master project which run all the tests in this project on a remote VM. ProjectSuite + Project01 + Master + NetworkSuite + Job01 + Task01 - Project01 (100 tests - 1-100) - VM01 I would like to add another task to Job01 to run half the tests on another VM. + Master + NetworkSuite + Job01 + Task01 - Project01 (50 tests - 1-50) - VM01 + Task02 - Project01 (50 tests - 51-100) - VM02 A test item can be specified in the command line as detailed in TestComplete Command Line (thanks @tristaanogre, @cunderw). /project:project_name /test:test_name test_name can be a test item/group. But specifying a test item in the "Test" field in a network suite task is not working. I would like network suite tasks also to recognize test ietms/groups so that a project with a large number of tests can be run on multiple slaves.2.3KViews2likes0CommentsRe: Click a variable
Also, if you want to specifically use the variable, and don't mind using xpath, you can do the following: dim b, obj, xpath b = "Hi How are you" xpath = "//*[text()='" & b & "']" Set page = Sys.Browser("*").Page("*") Set obj = page.FindChildByXPath(xpath) If the variable sting is not unique and there is more than one element in your page with the string, you will have to modify the xpath to get the desired object.1.6KViews0likes0CommentsRe: Using same Test in multiple Projects within a TestSuite
You can create a new blank keyword test in the second project and copy and paste the required (or all) keyword test steps from an existing test in the first project. But as tristaanogre said, it can become a maintenance nightmare pretty quicky.2.1KViews0likes0CommentsRe: Execute tests in a single project on 2 slaves
So, a test item can be specified in the command line as detailed in TestComplete Command Line (thanks tristaanogre, cunderw). /project:project_name /test:test_name test_name can be a test item. But specifying a test item in the "Test" field in a network suite task is not working. Can someone please confirm whether a test item can be specified in a task or not?2KViews0likes0CommentsRe: Running a subset of tests in a project
I want to run a subset of tests in a project (without creating a new project for them, if possible). More specifically, I have a project suite with 5 projects: Project 01 - 70 tests Project 02 - 120 tests Project 03 - 68 tests Project 04 - 50 tests Project 05 - 85 tests Running the project suite and all the 393 tests in it takes a long time and doing it more than once a day is not very effective. Sot I want to run a subset of the higher priority tests more frequently, which will give me a good idea about the state of my web app through the day and will also catch any major issues. These are the subset of tests that have been identified for that: Project 01 - 25 tests (out of 70 tests total) Project 02 - 40 tests (out of 120 tests total) Project 03 - 20 tests (out of 68 tests total) Project 04 - 15 tests (out of 50 tests total) Project 05 - 20 tests (out of 85 tests total) That adds up to 120 out of the 393 tests. As I mentioned in my initial description, I want to create 2 Jenkins jobs, one of them running 393 tests once a day and the other running 120 tests twice (or more) a day. I am looking for a way to execute the 120 tests in the above scenario. Hope the requirement is clear. Do let me know if there is still some confusion.2.9KViews0likes4CommentsRe: Running a subset of tests in a project
Hmm. The one project I gave above was just an example. We have multiple projects already in our test suite. So this will involve some rework and process changes moving forward. Also, I don't think it will be a good place to be in future when we have more tests and need to re-organize tests from either group, like moving tests from one group to the other. Is this the only way? Is there no way to tag a test in a project to belong to a group and then execute the group?2.9KViews0likes6CommentsRunning a subset of tests in a project
I have a project with 100 tests which I have set up with Jenkins to run on a schedule. I would like to run 2 jobs daily: A "smoke" job which runs 30 tests out of the 100 tests twice a day. A second job which runs all the 100 tests once a day. How can I group the "smoke" tests in a project as mentioned above? I found "How to Run a Group of Tests", but that talks about ordering the tests and nothing about running a specific group of tests.Solved3KViews0likes8CommentsRe: Execute tests in a single project on 2 slaves
I tried <Project>\TestItems\<TestItem> in the task and got a "not found" error. The "Editing Task Properties" page lists only keyword tests, script routines, low level procedures, project and "no value" as possible values. How do I specify the parent test item in a task?2.1KViews0likes1Comment