CallforTesting
|
Size: 3772
Comment:
|
Size: 4247
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| Coordinate with [[https://launchpad.net/~nskaggs|Nicholas Skaggs]] to setup a tracker for your software. You'll need to supply the following | Coordinate with [[https://launchpad.net/~nskaggs|Nicholas Skaggs]] to setup a tracker for your software. In order for a call for testing to work, the following will need to be addressed: |
| Line 24: | Line 24: |
| * The testcases can be simple smoke tests (like, "Does the application "work"?"), but ultimately we would like to add more in-depth testcases for specific funcationality. The testcase format should be as follows -- (the QA Community coordinator can help you with this): * Perform X action * Expect Y result * Create a ppa with builds for each of your target releases. * Create instructions for installing (something like add the ppa, and install X package) * Create instructions for uninstalling (usually just ppa purge works) * Create instructions for reporting a bug. It's important to note what package you want the bug report against, and if multiple packages, which one to report for which reason. You may choose to use ubuntu-bug, or provide a pre-formmatted link to 'report a bug' on launchpad. * Give the timeframe for testing, if applicable |
* If possible, contribute your testcases directly to the [[https://launchpad.net/ubuntu-manual-tests|ubuntu-manual-tests project]] * [[https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide|Style guide]] * [[https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual|Tutorial for contributing]] * The testcases can be simple smoke tests (like, "Does the application "work"?"), but ultimately we would like to add more in-depth testcases for specific functionality. The testcase format is [[https://wiki.ubuntu.com/Testing/TestCaseFormat#contribute|documented here]]. * If you don't have testcases, or are unable to contribute, coordinate with the QA Community Coordinator to have these tests created for you in order for your testing event to occur. * A ppa with builds for each of your target releases * Instructions for installing (something like add the ppa, and install X package) * Instructions for uninstalling (usually just ppa purge works) * Instructions for reporting a bug. It's important to note what package you want the bug report against, and if multiple packages, which one to report for which reason. You may choose to use ubuntu-bug, or provide a pre-formatted link to 'report a bug' on launchpad. * A timeframe for testing, if applicable |
| Line 34: | Line 36: |
| With those pre-requisites completed, the QA community coordinator will verify the application, tests and the ppa. A new milestone for your package will be created and and the link will be provided back to you. A wide call for testing will go out to the greater ubuntu community, and users will utilize the tracker to report results. | With those prerequisites completed, the QA community coordinator will verify the application, tests and the ppa. A new milestone for your package will be created and and the link will be provided back to you. A wide call for testing will go out to the greater ubuntu community, and users will utilize the tracker to report results. |
| Line 37: | Line 39: |
| As results come in, the tracker will update to reflect the number of contributors, what tests are passing or failing, and what bugs are reported. Everything is public and availible via the tracker. See the 'What does it look like?' section above. | As results come in, the tracker will update to reflect the number of contributors, what tests are passing or failing, and what bugs are reported. Everything is public and available via the tracker. See the 'What does it look like?' section above. |
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. The QA community can install and test your software for bugs and usability and provide bug reports and feedback using the qatracker.
What do I get?
As a developer, you will get consolidated feedback on how many people tested, the bugs reported, and any comments they may have left while testing. In addition, you will be able to see this for each of your versions of the software. This allows you to spot regressions and confirm fixes between versions.
What does it look like?
Have a look at the Kernel testing as an example. Let's point out the different pieces:
Testcases for the software. Notice the link to the installation instructions and bug reporting instructions. Also notice also the changelog showing the changes in this version at the top
Detailed results for the specifc version selected. Notice the usernames of the tester, bugs, the pass/fail indications and comments
A list of bugs, and more information about bug status found for each piece of software under test
Finally, here's information on how the users will use the site to submit results.
What do I need to do?
Coordinate with Nicholas Skaggs to setup a tracker for your software. In order for a call for testing to work, the following will need to be addressed:
- Testcases
If possible, contribute your testcases directly to the ubuntu-manual-tests project
The testcases can be simple smoke tests (like, "Does the application "work"?"), but ultimately we would like to add more in-depth testcases for specific functionality. The testcase format is documented here.
- If you don't have testcases, or are unable to contribute, coordinate with the QA Community Coordinator to have these tests created for you in order for your testing event to occur.
- A ppa with builds for each of your target releases
- Instructions for installing (something like add the ppa, and install X package)
- Instructions for uninstalling (usually just ppa purge works)
- Instructions for reporting a bug. It's important to note what package you want the bug report against, and if multiple packages, which one to report for which reason. You may choose to use ubuntu-bug, or provide a pre-formatted link to 'report a bug' on launchpad.
- A timeframe for testing, if applicable
Then what happens?
With those prerequisites completed, the QA community coordinator will verify the application, tests and the ppa. A new milestone for your package will be created and and the link will be provided back to you. A wide call for testing will go out to the greater ubuntu community, and users will utilize the tracker to report results.
Results
As results come in, the tracker will update to reflect the number of contributors, what tests are passing or failing, and what bugs are reported. Everything is public and available via the tracker. See the 'What does it look like?' section above.
Testing/CallforTesting (last edited 2013-04-25 18:45:07 by adsl-98-70-42-80)