RQM - 'Test Environment' usage for both 'variants' and 'SIL/HIL Test Env'
Currently we are using Test Environment to differentiate the different 'HW Variants' of a product.
Example: A Product can have different variants for A, B, C - which could be based on different HW or SW features.
Why: Because, for each of the variant i might use the same test - however need a specific 'Test Result' (linked to a specific 'Test Execution Record')
Problem: Today we have a need to differentiate the different Env. of tests - SIL/VIL/HIL etc
I know, Test Environment is to be exactly for this context - SIL/HIL etc. However need your support, to know - how best this could be handled. I mean, both SIL/HIL etc along with product variants.
The only option i see is :
1. A_SIL, A_HIL, B_SIL, B_HIL etc. (as part of Test Environment)
Do let me know, if there are other ways of doing it in RQM.
One answer
The most recommended way to get correct answer to this question is to consult a QM Solution architect who could provide most suited solution customized to your setup. However, you could also considering following alternative to manage your variance needs in your test setup.
1. Using Keywords in your Manual test scripts - It provides common steps being used across different versions of your product components. To learn more about keywords in test script refer - https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.rational.test.qm.doc%2Ftopics%2Ft_create_keywords.html
But this is mostly for Manual Tests.
2. Another possible way is using Channels. So you could create HW and SW channels for testing different version of your production component. But this is not highly recommended because it becomes difficult to manage channels when versions of components grow in future. Channels could be used for relatively stable platform such as product assembly line etc. To know more please refer - https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.rational.test.lm.doc%2Ftopics%2Fc_channels_overview.html
3. If you are using QM 6.0 or later versions then you could consider using Configuration Management in QM. This is designed to work with different version of the same test artifact.
Each test script could be customized to the HW and SW versions of your product component you have.
But you have to be careful before enabling Configuration Support in your project area. Go through following link before considering trying out with Configuration Management in QM.