canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Strategy/Integration vs End to end: Difference between revisions
Jump to navigation
Jump to search
B2G/QA/Automation/UI/Strategy/Integration vs End to end (view source)
Revision as of 18:00, 13 February 2015
, 13 February 2015→The Problem
| Line 12: | Line 12: | ||
= The Problem = | = The Problem = | ||
To date, UI automation has been treated as a single type of testing, with the differences expressed largely as to whether it was running on TBPL or not, was written in JS or Python, who sheriffed, and so forth. And so much discussion, debate, and analysis paralysis has involved whether the automation should be run, written, or treated a particular way. It has been all too common to reach an impasse based on differing opinions. | To date, FxOS UI automation has been treated as a single type of testing, with the differences expressed largely as to whether it was running on TBPL or not, was written in JS or Python, who sheriffed, and so forth. And so much discussion, debate, and analysis paralysis has involved whether the automation should be run, written, or treated a particular way. It has been all too common to reach an impasse based on differing opinions. | ||
But not all automation is the same just because it targets the UI, just as not all testing is the same just because it targets the SUT. | But not all automation is the same just because it targets the UI, just as not all testing is the same just because it targets the SUT. | ||