Test Run: Specify Environment and Build #
Hello,
We were looking for a way to include the build number and the environment in the test run. I cannot find a reasonable solution for including this data.
- We did not want the data to be free text fields as this is way too prone to error and we need to filter on this data.
- We explored a drop down, but this would be unmanageable for build and environments across all our Jama projects in one fields, especially since single select fields do not start to filter once your start typing in data.
- We explored over loading the Release field for build, but if we add release to test run it is not available during text execution
- I tried the same using Item of Type, but again this is not available in test run execution
- I thought we could use the categories, but again categories are not available at text execution.
- We looked at making this a required entry as the first test step, but we want this data in trace report getting only the first step would appear non trivial
- We could maybe use the cycle name as a build, but this might not map 100% of the time and we could have multiple environments on one cycle
Anyone have a semi elegant solution for add build and environment on the test run.
Regards
Jason
------------------------------Jason Barton
VMS
Palo Alto CA
------------------------------
Comments
-
Jason,
Did you try to use a Test Plan per environment and use the Cycle to manage the build ?
------------------------------
Frederic Fiquet
Hologic
------------------------------
-------------------------------------------
Original Message:
Sent: 03-05-2024 15:57
From: Jason Barton
Subject: Test Run: Specify Environment and Build #Hello,
We were looking for a way to include the build number and the environment in the test run. I cannot find a reasonable solution for including this data.
- We did not want the data to be free text fields as this is way too prone to error and we need to filter on this data.
- We explored a drop down, but this would be unmanageable for build and environments across all our Jama projects in one fields, especially since single select fields do not start to filter once your start typing in data.
- We explored over loading the Release field for build, but if we add release to test run it is not available during text execution
- I tried the same using Item of Type, but again this is not available in test run execution
- I thought we could use the categories, but again categories are not available at text execution.
- We looked at making this a required entry as the first test step, but we want this data in trace report getting only the first step would appear non trivial
- We could maybe use the cycle name as a build, but this might not map 100% of the time and we could have multiple environments on one cycle
Anyone have a semi elegant solution for add build and environment on the test run.
Regards
Jason
------------------------------
Jason Barton
VMS
Palo Alto CA
------------------------------
0 -
Jason Barton Member, Jama Connect Interchange™ (JCI), Jama Validation Kit (JVK) + Functional Safety Kit (FSK) Posts: 16
Frederic
We evaluated test plan as an option, but it would get really unruly trying to manage the different environments at the test plan level. Our Test Plan for a release or large testing effort. We have already duplicated test cases to satisfy different environments since we cannot have multiple test cases in a test plan. Ideally we would test multiple environments in one test cycle. We are exploring release as a definition of the build, but environment is still a bit of a challenge. Our testing team wants to specify this at test execution.
------------------------------
Jason Barton
VMS
Palo Alto CA
------------------------------
-------------------------------------------
Original Message:
Sent: 03-07-2024 07:59
From: Frederic Fiquet
Subject: Test Run: Specify Environment and Build #Jason,
Did you try to use a Test Plan per environment and use the Cycle to manage the build ?
------------------------------
Frederic Fiquet
Hologic
------------------------------
Original Message:
Sent: 03-05-2024 15:57
From: Jason Barton
Subject: Test Run: Specify Environment and Build #Hello,
We were looking for a way to include the build number and the environment in the test run. I cannot find a reasonable solution for including this data.
- We did not want the data to be free text fields as this is way too prone to error and we need to filter on this data.
- We explored a drop down, but this would be unmanageable for build and environments across all our Jama projects in one fields, especially since single select fields do not start to filter once your start typing in data.
- We explored over loading the Release field for build, but if we add release to test run it is not available during text execution
- I tried the same using Item of Type, but again this is not available in test run execution
- I thought we could use the categories, but again categories are not available at text execution.
- We looked at making this a required entry as the first test step, but we want this data in trace report getting only the first step would appear non trivial
- We could maybe use the cycle name as a build, but this might not map 100% of the time and we could have multiple environments on one cycle
Anyone have a semi elegant solution for add build and environment on the test run.
Regards
Jason
------------------------------
Jason Barton
VMS
Palo Alto CA
------------------------------
0
