MozillaWiki

SoftwareTesting: Difference between revisions

Page Discussion

SoftwareTesting (view source)

Revision as of 23:16, 7 September 2010

1,036 bytes added ,  7 September 2010
→‎Areas/concepts to investigate
 
(22 intermediate revisions by 7 users not shown)
Line 10: Line 10:
=Projects=
=Projects=
==Testing in General==
==Testing in General==
[[User:Davel|Dave Liebreich]] is interested in creating running code to test the mozilla codebase. Not just end-to-end automated tests, but unit tests, module tests, test harnesses, test reporting infrastructure, and anything else that lowers the barrier to creating new code that gives someone feedback.
We need your help! There is a small but growing set of software tools for testing Firefox functionality. Please see [http://developer.mozilla.org/en/docs/Mozilla_automated_testing MDC:Mozilla_automated_testing] for details on what we have currently.


Dave is also interested in extending and improving the existing testing process.  The information received from community testing efforts can be excellent and invaluable; Dave is looking for ways in which existing volunteers can improve their testing skill and skilled testers can join the effort.
Dave needs help.  The codebase is huge.  The community is huge.  The task is huge.
* [[SoftwareTesting:Watir and Firefox]] - Writing the code necessary for [http://wtr.rubyforge.org/ Watir] to drive Firefox
* [[SoftwareTesting:BBST and the Mozilla Codebase]] - Using mozilla-based apps and libraries as coursework examples and exercises in [http://testingeducation.org/BBST/index.html A Course in Black Box Testing]
* [[SoftwareTesting:TDD and the Mozilla Codebase]] - Infrastructure, support, and examples of using TDD in mozilla projects
==Black-Box Testing==
==Black-Box Testing==
* [[SoftwareTesting:BlackBoxTesting]]
* [[SoftwareTesting:BlackBoxTesting]]
Line 36: Line 29:
** xforms tests written using jsUnit
** xforms tests written using jsUnit
* FireWatir
* FireWatir
* jUnit/FIT + javaxpcom
* jUnit/FIT + javaxpcom - See [http://www.sirgroane.net/2010/09/automated-javascript-unit-tests-with-xpcshell-and-hudson howto integrate xpcshell and hudson]
* pyUnit/pyFIT + pyxpcom
* pyUnit/pyFIT + pyxpcom
* webdav extension test harness (precursor to some calendar tests)
* webdav extension test harness (precursor to some calendar tests)
Line 42: Line 35:
** what can we use/re-use
** what can we use/re-use
* [[SoftwareTesting:2006-06-26 Brainstorm]]
* [[SoftwareTesting:2006-06-26 Brainstorm]]
==Wishlist for xpcshell test harness==
* Ability to mark tests as XFAIL when they are known to fail at the moment
* non-fatal do_check_* (as new functions) to be able to see all the test failures, not just the first one


=Tools=
=Tools=
* [[SoftwareTesting:Catalog of Automated Tests]] - a list of pointers to existing automated tests in the mozilla codebase
* [[SoftwareTesting:Catalog of Automated Tests]] - a list of pointers to existing automated tests in the mozilla codebase
* [https://bugzilla.mozilla.org/show_bug.cgi?id=test-harness Tracking bug] for work on mozilla test harnesses
* {{bug|test-harness}} tracking bug for work on mozilla test harnesses
* [[SoftwareTesting:Tools:Simple xpcshell test harness]] - project tracking page
* [[SoftwareTesting:Tools:Simple xpcshell test harness]] - project tracking page
* [[SoftwareTesting:Tools:JsshDriverPython]]
* [[SoftwareTesting:Tools:JsshDriverPython]]
* [[SoftwareTesting:Tools:TestRunnerPython]]
* [[SoftwareTesting:Tools:TestRunnerPython]]
* [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=&branchtype=match&dir=mozilla%2Ftesting&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=month&mindate=&maxdate=&cvsroot=%2Fcvsroot Updates to Testing Module]
* [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=&branchtype=match&dir=mozilla%2Ftesting&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=month&mindate=&maxdate=&cvsroot=%2Fcvsroot Updates to Testing Module]
* [http://developer.mozilla.org/samples/domref/dispatchEvent.html Example code] for simulating a click in js
* [http://www.openjsan.org/doc/t/th/theory/Test/Simple/0.21/ JSAN Version] of Perl's Test::Simple and related modules
* {{bug|test-suites}} tracking bug for adding tests to test suites
* [[SoftwareTesting:Tools:BrowserShutdown|How to shut down the browser]]


=People=
=People=
* [[User:Davel|Dave Liebreich]]
* [[User:Rcampbell|Rob Campbell]]
* [http://developer.mozilla.org/en/docs/User:ChrisCooper Chris Cooper]
* [[User:Bhearsum|Ben Hearsum]]
* [[User:Rhelmer|Rob Helmer]]
* [[User:Anodelman|Alice Nodelman]]
* [[User:Ctalbert|Clint Talbert]]
 
=Ideas to Collect=
(stuff that needs to be organised)
* [[SoftwareTesting:Tools:jsUnit]]
* [[SoftwareTesting:Tools:SimpleXulTestHarness]]
* example extension test using foxunit
** davel thinks xul/js-run-as-chrome is probably better
* jsunit in chrome proof-of-concept - [http://lxr.mozilla.org/mozilla/source/toolkit/mozapps/update/src/testnsUpdateService.js file] and Makefile.in in the same directory
* dbaron's [http://lxr.mozilla.org/mozilla/source/layout/tools/reftest/ layout reftest stuff]
** uses copy of domi code to handle command-line args in both firefox and seamonkey
* continuous integration/test issues
** {{bug|351968}} filed to track ENABLE_TEST issues
** build team has decided to avoid spending time getting new things to work with tinderbox
*** we need a tinderbox replacement, so this would be wasted time
** if a new test can be run in a manner very similar to an existing tinderbox feature, then it probably will be added
* aus2 tests using pyFit/fitnesse
** check-in pending from morgamic
[[Category:SoftwareTesting]]
IanRogers
1

edit

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/28911...251570"