Actions

Difference between revisions of "Bug Squad Automated Testing Team"

From Joomla! Documentation

(Overview)
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.
  
 
== Overview ==
 
== 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.
 
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 in run a daily basis in conjunction with the nightly build. The individual tests and test suite can also be run manually on an end-users workstation. When they are run, failures and errors will be displayed at the end of the test suite. These failures and errors will indicate where changes or regressions may have occurred. The person running the test(s) can then investigate whether the issue stemmed from
  
 
== System & Unit Testing ==
 
== System & Unit Testing ==

Revision as of 07:51, 27 May 2010

Workgroups bugsquad.jpg
Quill icon.png
Page Actively Being Edited!

This article is actively undergoing a major edit for a short while.
As a courtesy, please do not edit this page while this message is displayed. The user who added this notice will be listed in the page history. This message is intended to help reduce edit conflicts; please remove it between editing sessions to allow others to edit the page. If this page has not been edited for several hours, please remove this template, or replace it with {{underconstruction}} or {{incomplete}}.

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 in run a daily basis in conjunction with the nightly build. The individual tests and test suite can also be run manually on an end-users workstation. When they are run, failures and errors will be displayed at the end of the test suite. These failures and errors will indicate where changes or regressions may have occurred. The person running the test(s) can then investigate whether the issue stemmed from

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