Absent Member.
Absent Member.

Test Executions

I'm trying to understand the definitions / concepts and relationships within SCTM regarding the following:

  • Child testing cycle
  • Child configuraion suite
  • Chil execution plan
  • and the relationships to tests (1 to 1 or many to 1)

The definitions in the online help are 99% non-existent as far as I can tell. There are very simple instructions on how to click buttons and view things etc. - but no real help or examples on the relationshis between these things and how they should ideally be used. Keeping in mind with all process related items that the MF defintion of a test cycle will most likely differ from many other definitions on the internet and from other vendors. So these things cannot be assumed.

thanks Marc

4 Replies

Hi Marc,

The „lowest“ object is the Execution Plan.

Execution Plan:Test = m:n

The concept is the ability to specify a set of tests which is then executed by a manual tester or an execution server at a specific point in time.

Configuration Suite is in the end an extension of an folder where you can define configurations where each configuration becomes an child execution plan with specific keywords and parameters.

Configuration Suite:Test = m:n -> each of the child execution plans has the same set of tests

Configuration Suite (Tests)

|- Execution Plan 1 (Tests, Keywords[…], Parameters[…])

|- Execution Plan 2 (Tests, Keywords[…], Parameters[…])

|- Execution Plan 3 (Tests, Keywords[…], Parameters[…])

The concept is that the same set of tests is executed against different configurations.

A test cycle is also a specific folder with additional information about a time frame (start, end), and assigned testers with their available capacity within this time frame. The test cycle as shown in the Execution Planning is the “backend” for the things that are done in the Manual Execution Planning. Depending on usage of configurations, test containers, etc. different execution plans are created automatically – at least for each assigned tester one execution plan is created.

Test Cycle:Test=m:n

The idea is to give the user some management capability around the execution of manual tests, with given resources in a specific time frame.



Product Owner - Silk
Absent Member.
Absent Member.

OK - thanks Florian - got most of that. A few more questions please.

1.  In the example above with Configuration suite and child execution plans, why would each of the child execution plans have the same set of tests with simply different keywords / parameters? Can you give a few decent examples please?

2.  Testing cycles – I can see how they have date periods and manual testers are assigned with a capacity, but I cannot see the relationship with tests or configuration suites or executions plans. Can I please ask that you explain this in much more detail, again with some decent examples please?

Many thanks Marc

Absent Member.
Absent Member.

Heloooooo - any chance of getting a response to this please?

Micro Focus Expert
Micro Focus Expert

  1. Configuration testing is for testing a system with each of the supported software and hardware configurations.
    eg.: you want to automated test your software on Oracle10 and MsSQL2012. Here you would create a Configuration Suite with two Configurations:
    1. Configuration Oracle10 - with parameters dbType=Oracle, dbHost=orcl10Server
    2. Configuration MsSQL2012 - with parameters dbType=MsSQL, dbHost=sql2012Server

      Now you are able to execute all your tests against the supported databases. This can even be done in parallel. If you have to support an additional database in future (eg.: Oracle12) you just have to add a Configuration and all your tests will also run against the new database without having to change anything on your test set.

      This concept can also be used for manual testing.
      eg.: The test step description is: Connect the product to database server ${dbHost}. This placeholder will be replaced depending on the Configuration you are executing. So one manual tester will test against orcl10Server and the other tester against sql2012Server without the need of 2 different versions of the manual test.

  2. When using Testing Cycles the Execution Plans are handled in the background as there is a comfortable Manual Execution Planning UI for this. You just specify which tests should be executed by whom in this timespan. When starting the Testing Cycle the needed Execution Plans (with test and tester assignment) are created by the system. In a Testing Cycle you can also specify the Configurations a test should be executed. eg.: The manual test "Order Item" should be executed on all supported systems.
    1. You create Configurations "English|Oracle10g|IE8" and "German|SQL2008|Firefox" and "English|SQL2012|Chrome"
    2. Assign test to Testing Cycle
    3. Specify the Configurations this test should be executed in this Testing Cycle

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.