Feature request, copy an answer set, but apply a new version of the RS or AT

[GeorgeKerscher]

It takes a long time to complete a answer set and only one or two items may change. For example, when NVDA 22021.3 comes out, the test results will likely be almost identical. I would like to copy this answer set using the new NVDA 2021.3 as the only change. I could also go in and update any test result that may have changed. This would save a ton of time.

[marisademeglio]

Notes from the call on 9 Nov 2021:

Group decision to remove version numbers from testing environment software profiles and collapse results into an "evergreen" profile. Note latest tested version numbers in summary field.

[marisademeglio]

Idea:

Unversion software entries, put the version numbers on the answer sets instead.

So a testing environment is a stack of software, like before, but that software is not versioned.

And, when you add an answer set, you can also choose to copy the old answers over if they exist.

This might be a lot of work to refactor.

[GeorgeKerscher]

My understanding is that we will eventually update the website results to show the latest set of tests and in the results we will have one entry for each language, e.g., German would have its own set of entries. So, a test environment may be Windows, Thorium Reader, NVDA and the details for the version of Windows, the version of Thorium Reader, and version of NVDA would be in the test results. I want to confirm this on the discussion list. My questions would be do we want to have test environments for major updates, e.g., Windows 11 would have all new test environments. All-in-all, this should simplify and speed up the reporting of new test results.

[marisademeglio]

I see three things here:

• Copy old results to new results
• Use evergreen versioning for testing environments
• Attach language information

I am opening separate issues for the latter 2 items (#66, #67) to keep things organized.

My opinion is that Windows 11 would not warrant its own set of entries - if we go with evergreen versioning, we should commit to just "Windows" at the testing environment level and list versions at the results level.