Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gliffy Diagram
nametest_environments
pagePin29


Note: If you don't use Test Environments, then only the latest result matters for assessing the current status of the Test.

...


StatusWhy?
windowsPASSdue to the last result obtained in "windows" environment on CALC-5262
macPASSdue to the last result obtained in the "mac" environment on CALC-52625263
edgechromeFAILdue to the last result obtained in "chrome" environment on CALC-5261
chromeedgePASSdue to the last result obtained in "edge" environment on CALC-5263

"All Environments"

(if analyzing the status of the test without identifying a specific environment)

FAILas the last result for one of the environments ("chrome") was FAIL (i.e. on CALC-5261)

...

Info
titleLearn more

For advanced Test Environment management capabilities, please check our Integration with Apwide Golive.

Don'ts

  • Don't create dozens or hundreds thousands of Test Environments as it will harden their usage and add some performance overhead
  • Don’t make composed environment names, such as ”<os>_<browser>_<stage>” as it will pollute the environment namespace and harden management
  • Don't try to do data-driven testing using Test Environments; they're not tailored for that

...

Info
titlePlease note

Besides other usage issues, if you have a large number of environments (>>10>500), it will impact the calculations that need to be done and the size of the Lucene index.

Please try to have a limited, restricted, and well-defined list of Test Environments.