Monthly Server Testing

Friday, December 27, 2019
Avatar

I have almost 150 servers that are regularly patched and tested after patching. Planning an initial round of update/testing for all 150 servers. Subsequently will do regular monthly updates for subsets of the 150 servers. Would like to set up Releases in Spiratest, add the servers to the appropriate release and associate test scenarios and scripts to the servers, test and document the results.  And then reuse test scripts in next release. Tried setting up each server as a requirement but once the requirement is added to a release it cannot be added to another release. 

Do I load up the set of servers again for the next release?  Or  would it be better to create the servers as a custom list and add them to releases?  Or is using components a better pathway? Has anyone else set up repetitive testing for a set of servers? 

2 Replies
Monday, January 6, 2020
Avatar
re: pbuickerood1 Friday, December 27, 2019

You can map the test case many to many to releases. Would that work for you?

Otherwise you can create a custom list MultiList property of the names of servers and add that to requirements and releases.

Wednesday, February 23, 2022
Avatar
re: pbuickerood1 Friday, December 27, 2019

We need associations between releases and requirements too. Telling the truth we need associations (and their different types) between all entities including tasks (additionaly to direct including task/requirement into the release that is how it is done now).

See my topic: Releases, Associations tab, proposal - Thread - Inflectra

Statistics
  • Started: Friday, December 27, 2019
  • Last Reply: Wednesday, February 23, 2022
  • Replies: 2
  • Views: 1302