Forum Discussion

jose_pjoseph's avatar
jose_pjoseph
Contributor
7 years ago
Solved

Running 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 secon...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    I'm not very familiar with the integration between TestComplete and Jenkins... however, as a command line, you can tell TestComplete/TestExecute to run a test item.  So, if you create a "parent" test item that "contains" the ones that you want to run, you can call that via command line.  See https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/command-line.html#command-line-arguments and reference the "/test:" command line switch.

     

    If you organize your tests appropriately, you can call a batch that way. 

  • cunderw's avatar
    cunderw
    7 years ago

    If test items are being used for your project under organize tests then you can group your test items under a parent.

     

    So test items for Project 01 would look like:

    • SmokeTest
      • Test 1
      • Test 2
      • Test ...
      • Test 25
    • Test 26
    • Test ...
    • Test 70

     

    Then on jenkins for your smoke tests job you can specify Project Test when setting up the Test Complete step and use SmokeTest.

     

    For the full run job you can then do the entire suite option

jose_pjoseph's avatar
jose_pjoseph
Contributor

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:

  1. Project 01 - 70 tests
  2. Project 02 - 120 tests
  3. Project 03 - 68 tests
  4. Project 04 - 50 tests
  5. 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:

 

  1. Project 01 - 25 tests (out of 70 tests total)
  2. Project 02 - 40 tests (out of 120 tests total)
  3. Project 03 - 20 tests (out of 68 tests total)
  4. Project 04 - 15 tests (out of 50 tests total)
  5. 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.

  • cunderw's avatar
    cunderw
    Community Hero
    7 years ago

    If test items are being used for your project under organize tests then you can group your test items under a parent.

     

    So test items for Project 01 would look like:

    • SmokeTest
      • Test 1
      • Test 2
      • Test ...
      • Test 25
    • Test 26
    • Test ...
    • Test 70

     

    Then on jenkins for your smoke tests job you can specify Project Test when setting up the Test Complete step and use SmokeTest.

     

    For the full run job you can then do the entire suite option

    • jose_pjoseph's avatar
      jose_pjoseph
      Contributor
      7 years ago

      Thanks tristaanogre & cunderw! /test:<TestItem> does what I need. I will try that in my Jenkins setup and see if I can make the Jobs work.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    7 years ago

    I'm not very familiar with the integration between TestComplete and Jenkins... however, as a command line, you can tell TestComplete/TestExecute to run a test item.  So, if you create a "parent" test item that "contains" the ones that you want to run, you can call that via command line.  See https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/command-line.html#command-line-arguments and reference the "/test:" command line switch.

     

    If you organize your tests appropriately, you can call a batch that way.