0

My Client has an application which will be working on Desktop Browsers, Mobile Brosers and as a Native app on both Android and iPad. Currently we as test team propsed using Selenium for Web Automation & Combination of Selenium+ SeeTest for web Browser & Native apps. But issue is we are scripting the flows 3 times owing to 3 different platforms. What would be the best strategy to handle this situation?

eugene.polschikov
  • 7,254
  • 2
  • 31
  • 44
Saurabh Seth
  • 43
  • 1
  • 2
  • 7

1 Answers1

0

You can avoid

we are scripting the flows 3 times owing to 3 different platforms.

by utilizing Write once, test everywhere pattern. The concept centers advantage of shared behavior between multiple implementations of one application. For example it should be possible to purchase a product from your website no matter if user uses desktop, mobile or native application. This is also know as pluggable pattern (and architecture). It could like this:

Plugin architecture

Used properly it will give you: foresight (boil down every test case), reusability and simplicity. There are disadvantages as well (but I think there is no escape from those anyway):

  • Runtime context switching
  • Complex code base

Aiming at full answer here, you can consider the Test harness concept. It propose separation of all your code into three major concerns (SoC):

  • Execution engine (plugins)
  • Tests (BDD)
  • Configuration (as code)
ekostadinov
  • 6,880
  • 3
  • 29
  • 47