CallforTesting

Revision 1 as of 2012-03-12 19:10:40

Clear message

THIS IS STILL A WORK IN PROGRESS

Summary

A call for testing is meant to call attention to a particular piece of software for testing over a short time-frame in order to confirm and resolve and bugs and ready for general consumption.

Developer Tasks

As a developer, there are a few things to do in order to ready your code for testing.

  • Make sure you have written unit tests, and ideally perhaps some other automated testing
    • In addition, make sure all of your testcases pass Smile :-)

  • Create a ppa with builds for each of your target releases.
  • Add source hooks to your ppa so apport will properly report crashes with your software. Please ensure you specify a unique tag for apport to report your bugs with. This allows for ease reporting and allows for metrics and summaries to be generated.

  • Create/Modify the testcases for your piece of software that you wish to have users run. The current preferred testcase delivery format is checkbox. Please reference this page regarding contributing new testcases if necessary. Once your application has a set of testcases, asking for testing will only require you to write a test(s) for the new feature, and the other tests will still be executed so that you'll get regression testing as well.

  • Fill out this form. It just gathers some basic information on where your ppa is at and the timeline for testing.

QA Tasks

With those pre-requisites completed, the QA community coordinator will verify the application, tests and the ppa. Next, the manual application testing ppa for checkbox will be updated to include the new checkbox tests for the application. Then a call for testing to the greater community will be issued. The general guidelines will be to include the information given on the form about timeline and new feature description. The tester will download and install the software from the developer ppa, and if necessary install the checkbox ppa to get the application tests. The user will execute the tests using checkbox for the application and submit any crashes or bug reports generated by the testing.

Results

Once testing is completed, the results of the tests will be publicly available on the results tracker, and all bug reports should be available by querying launchpad for the specific bug-tag specified.