Actions

Difference between revisions of "Bug Squad Automated Testing Team"

From Joomla! Documentation

(General Procedure & Goals)
(4 intermediate revisions by one user not shown)
Line 1: Line 1:
 
[[Image:workgroups_bugsquad.jpg|right]]
 
[[Image:workgroups_bugsquad.jpg|right]]
{{inuse}}
+
 
 
== News and Updates ==
 
== News and Updates ==
2010 05 24 document created.
+
* 2010 05 24 document created.
2010 05 27 document updated with General Procedure & Goals section.
+
* 2010 05 27 document updated with General Procedure & Goals section.
  
 
== Overview ==
 
== Overview ==
Line 13: Line 13:
 
As of this writing, the system test suite is run a daily basis in conjunction with the nightly build. The individual tests and test suite can also be run manually on an end-user's workstation. When they are run, failures and errors will be displayed at the end of the test, if there are any. These failures and errors will indicate where changes, regressions, bugs or other issues may have occurred. The person running the test(s) can then investigate whether the issue(s) stemmed from a bug or a programmatic change. Programmatic changes (i.e. renaming "jformparent_id" to "jform_parent_id") generally occur quite often during development and beta stages and are corrected on the test level.
 
As of this writing, the system test suite is run a daily basis in conjunction with the nightly build. The individual tests and test suite can also be run manually on an end-user's workstation. When they are run, failures and errors will be displayed at the end of the test, if there are any. These failures and errors will indicate where changes, regressions, bugs or other issues may have occurred. The person running the test(s) can then investigate whether the issue(s) stemmed from a bug or a programmatic change. Programmatic changes (i.e. renaming "jformparent_id" to "jform_parent_id") generally occur quite often during development and beta stages and are corrected on the test level.
  
Ultimately, our goal is to have a system test submitted with each patch. Each submitted system test can be integrated into the test suite and ensure future functionality and prevent regressions.
+
Ultimately, our goal is to have a system test submitted with each patch. Each submitted system test can be integrated into the test suite and ensure future functionality and prevent regressions. Please see [[Writing_System_Tests_for_Version_1.6]] for more information.
  
 
== System & Unit Testing ==
 
== System & Unit Testing ==
Line 32: Line 32:
 
* Join the Joomla! bug Squad group at http://people.joomla.org/groups/viewgroup/95-Joomla+Bug+Squad.html
 
* Join the Joomla! bug Squad group at http://people.joomla.org/groups/viewgroup/95-Joomla+Bug+Squad.html
 
* See the category links below
 
* See the category links below
[[Category:Development Working Group]][[Category:Bug Squad]][[Category:Automated Testing]]
+
[[Category:Development Working Group]][[Category:Bug Squad]][[Category:Testing]][[Category:Automated Testing]]
 +
[[Category:Working Groups]]

Revision as of 03:46, 20 September 2010

Workgroups bugsquad.jpg

Contents

News and Updates

  • 2010 05 24 document created.
  • 2010 05 27 document updated with General Procedure & Goals section.

Overview

Automated testing is a key technology being incorporated into the workings of JBS. At the present, this is a somewhat specialized skill, and a team of people who are familiar with this will help write automated tests and train other JBS members on automated testing. Our aim is to eventually make automated testing a routine part of fixing issues.

To follow the analogy from the Bug_Squad_Coding_Team doc, if the Bug Squad was run like a hospital, then the Automated Testing Team is like your doctor whom you see for your a regular checkup just to make sure everything is fine. If something is found not be quite right, we'll send you to see a specialist to get checked out and treated.

General Procedure & Goals

As of this writing, the system test suite is run a daily basis in conjunction with the nightly build. The individual tests and test suite can also be run manually on an end-user's workstation. When they are run, failures and errors will be displayed at the end of the test, if there are any. These failures and errors will indicate where changes, regressions, bugs or other issues may have occurred. The person running the test(s) can then investigate whether the issue(s) stemmed from a bug or a programmatic change. Programmatic changes (i.e. renaming "jformparent_id" to "jform_parent_id") generally occur quite often during development and beta stages and are corrected on the test level.

Ultimately, our goal is to have a system test submitted with each patch. Each submitted system test can be integrated into the test suite and ensure future functionality and prevent regressions. Please see Writing_System_Tests_for_Version_1.6 for more information.

System & Unit Testing

Automated Testing is comprised of two types of tests, System and Unit Tests. System test simulate and test what a user may experience where as Unit tests check individual blocks of source code.

For a good comparison of the two, see System Testing versus Unit Testing

Getting Started

To get started with Automated Testing, there are a few prerequisites:

Other Resources