QA/TDAI/Automation Software: Difference between revisions

From MozillaWiki
< QA‎ | TDAI
Jump to navigation Jump to search
m (trying to clean up spurious table html showing through)
m (more cleanup - got there in the end)
Line 47: Line 47:
<td><ul><li>someone in China is already working to automate testing of Firefox (1.0.6)</li></ul></td>
<td><ul><li>someone in China is already working to automate testing of Firefox (1.0.6)</li></ul></td>
<td><ul><li>Requires Gnome</li>
<td><ul><li>Requires Gnome</li>
<li>Reliant on accessibility hooks.</li></ul>
<li>Reliant on accessibility hooks.</li></ul></td>
<td>Under investigation (coop)</td>
<td>Under investigation (coop)</td>
</tr>
</tr>
Line 62: Line 62:
<td><ul><li>promises automated and "hidden" testcase generation</li></ul></td>
<td><ul><li>promises automated and "hidden" testcase generation</li></ul></td>
<td><ul><li>Reliant on expert domain knowledge (hard to get) to seed testcase generation.</li>
<td><ul><li>Reliant on expert domain knowledge (hard to get) to seed testcase generation.</li>
<li>No existing examples (that are accessible at least)</li></ul>
<li>No existing examples (that are accessible at least)</li></ul></td>
<td>Waiting on feedback from Edjard and/or Monica. We tasked them to provide some proof-of-concept testcases for Software Update and Preferences.</td>
<td>Waiting on feedback from Edjard and/or Monica. We tasked them to provide some proof-of-concept testcases for Software Update and Preferences.</td>
</tr>
</tr>
Line 78: Line 78:
<li>Designed for use in testing</li></ul></td>
<li>Designed for use in testing</li></ul></td>
<td><ul><li>Drives IE, not FF</li>
<td><ul><li>Drives IE, not FF</li>
<li>Designed for testing web app, not browser</li></ul>
<li>Designed for testing web app, not browser</li></ul></td>
<td>davel to investigate</td>
<td>davel to investigate</td>
</tr>
</tr>

Revision as of 18:28, 15 May 2006

Software Advantages Disadvantages Status
Spider
  • acts as test harness for various suites of tests: JS, DOM, top site
  • Developer (Bob Clary) on staff
 In use on QA test farm.
Selenium
  • Designed for web application testing, not end-to-end browser testing.
 Under investigation
Eggplant
  • Cross-plaform (uses VNC)
  • Bitmap-based testing is inherently fragile.
 Coop is working with Eggplant on the test farm to generate some proof-of-concept tests.
TestGen4Web
  • Designed for web application testing, not end-to-end browser testing.
 Under investigation
dogtail
  • Python-based: would be easy to extend
  • Reliant on accessibility hooks.
  • still very alpha
 Under investigation (bc)
LDTP
  • someone in China is already working to automate testing of Firefox (1.0.6)
  • Requires Gnome
  • Reliant on accessibility hooks.
 Under investigation (coop)
Tomato Under investigation (coop)
Grubzilla
  • promises automated and "hidden" testcase generation
  • Reliant on expert domain knowledge (hard to get) to seed testcase generation.
  • No existing examples (that are accessible at least)
 Waiting on feedback from Edjard and/or Monica. We tasked them to provide some proof-of-concept testcases for Software Update and Preferences.
Tracer
  • architecture is interesting
  • Captures a lot of information that we don't really care about.
 Possibly reuse this design pattern in the future, but the tool itself is of limited use.
WATIR
  • Used by many in the testing community
  • Designed for use in testing
  • Drives IE, not FF
  • Designed for testing web app, not browser
 davel to investigate
SAMIE
  • Designed for use in testing
  • Drives IE, not FF
  • Very little recent activity
 davel to investigate
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/TDAI/Automation_Software&oldid=26027"