Difference between revisions of "MULTIPLE PLATFORMS"

From Test Automation Patterns
Jump to navigation Jump to search
m (Topic titles in capital letters)
 
Line 14: Line 14:
 
* <span style="font-size: 16px">[[THINK OUT-OF-THE-BOX]]: try to look at the problem from unusual viewpoints</span>
 
* <span style="font-size: 16px">[[THINK OUT-OF-THE-BOX]]: try to look at the problem from unusual viewpoints</span>
 
<br /> <span style="font-size: 16px">Other useful patterns:</span><br />  
 
<br /> <span style="font-size: 16px">Other useful patterns:</span><br />  
* <span style="font-size: 16px">[[TEST AUTOMATION FRAMEWORK]]</span>
+
* <span style="font-size: 16px">[[TEST AUTOMATION FRAMEWORK]]: this pattern will help you implement other patterns, for instance [[ABSTRACTION LEVELS]]</span>
 
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div>
 
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div>

Latest revision as of 16:14, 27 June 2018

.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues

Issue Summary

The same tests are supposed to run in many different operating systems or browsers

Category

Design

Examples

The tests have to run with different database systems (for instance Oracle, MySQL etc.)
The tests have to run on different browsers (for instance Internet Explorer, Firefox, Chrome etc.)

Questions

Can you list exactly on what systems the tests are supposed to run?
Is the test execution really identical?

Resolving Patterns

Most recommended:

  • ABSTRACTION LEVELS: use this pattern to isolate the technical implementation. In this way you will be able to keep platform differences to a minimum
  • GET ON THE CLOUD: use this pattern to implement efficiently different platforms
  • THINK OUT-OF-THE-BOX: try to look at the problem from unusual viewpoints


Other useful patterns:


.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues