I have been thinking about this for some time and believe I have finally come up with a simple (in concept) solution. Instead of stopping at the first failing environment, the system should stop within "groups" defined by the plugin associated with the environment.
Meaning if I have 3 databases being tested with the SimpleTest plugin, coder review, and performance testing on two machines configurations the following would occur.
All 3 databases would only run if each passes, meaning once one fails those left will not. Coder review will always run since it is only in one environment. Performance will run on at least one machine configuration.
Comments
Comment #1
boombatower commentedpifr_server_test_result() - logic needs to be changed to follow.
messages/e-mails need to be updated to allow for multiple environments being the source of the error.
Comment #2
boombatower commentedComment #3
boombatower commentedThis will obviously require the summary messages and such to change along with this. I am thinking to solve a number issues that would be noticed down the road with more environments and #632212: Report # of passes even on success, make the summary message plugin centric.
For example:
Comment #4
boombatower commentedLocations that reference pifr_server_result_summary_message() which will need to be updated:
Comment #5
boombatower commentedComment #6
boombatower commentedCommitted.