Skip to main content
Jump to: navigation, search

Difference between revisions of "CDT/Obsolete/Manual Testing"

< CDT‎ | Obsolete
(Testing Coordination and Signup)
m (Jonah.kichwacoders.com moved page CDT/Manual Testing to CDT/Obsolete/Manual Testing)
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{warning|Note: The contents of this page is obsolete, but it may still contain some interesting tid-bits. The Manual Testing is now part of the [[https://github.com/eclipse-cdt/cdt-infra/issues?q=is%3Aissue+label%3Aendgame endgame]] checklist}}
 +
 +
[[Category:CDT:Obsolete]]
 +
 
This is the main page for manual testing effort in the CDT project.  Ideally the manual testing effort should help verify that a given release or build meets a certain quality standard.  However, the CDT project relies on volunteers to contribute their time to make the project what it is.  This page is designed to coordinate the efforts of volunteer testers to achieve maximum coverage and to assess the test completeness.
 
This is the main page for manual testing effort in the CDT project.  Ideally the manual testing effort should help verify that a given release or build meets a certain quality standard.  However, the CDT project relies on volunteers to contribute their time to make the project what it is.  This page is designed to coordinate the efforts of volunteer testers to achieve maximum coverage and to assess the test completeness.
  
Line 15: Line 19:
 
[complete], [complete: no bugs] or [complete: bug 123456, bug 123457] and it can be added next to your name to affect all tests, or next to individual tests for a more detailed status.
 
[complete], [complete: no bugs] or [complete: bug 123456, bug 123457] and it can be added next to your name to affect all tests, or next to individual tests for a more detailed status.
  
== Testing  Coordination and Signup ==
+
== Testing  Coordination ==
 +
 
 +
<!-- [[CDT/Manual Testing Signup Template]] -->
 +
* [https://docs.google.com/spreadsheets/d/14RzAFhKvqQaQ_PWi9XDopI-BFx-qtnMj4qRoz0KUW6E/edit?usp=sharing CDT 9.5.0 Testing]
 +
* [https://docs.google.com/spreadsheets/d/1LRoIll1N4_KkIj2rP1PdTmhmp8w06AOhFnknpuRiWeU/edit?usp=sharing CDT 9.2.0 Testing] (CDT 9.2 testing was not actually done/coordinated and this document is not public.)
 +
* [https://docs.google.com/spreadsheets/d/1RzC3A7n7PSEEDEViZt_PmndUc7H41CFy3tt0byMJLZ0/edit?usp=sharing CDT 9.1.0 Testing]
 +
 
 +
* [https://docs.google.com/spreadsheets/d/1u8pQ0fJQkXdGTkFN6PgdlXHvGe6rv_e200gVyrP5Bzg/edit?usp=sharing CDT 9.0.0 Testing]
 +
* [https://docs.google.com/spreadsheets/d/1W3LEUWx2QYK99yJOQavwOSwG6H0R6gCBagCW9kid4_U/edit?usp=sharing CDT 8.8.0 Testing]
 +
 
 +
* [[media:CDT_Testing_8.7.0.pdf | CDT 8.7.0 Testing]]
  
[[CDT/Manual Testing Signup Template]]
+
* [[media:CDT_Testing_8.6.0.pdf | CDT 8.6.0 Testing]]
  
* Future CDT 8.5 testing
+
* [[media:CDT_Testing_8.5.0.pdf | CDT 8.5.0 Testing]]
  
* [[media:CDT_Testing_8.4.0.pdf | CDT 8.4 Testing]]
+
* [[media:CDT_Testing_8.4.0.pdf | CDT 8.4.0 Testing]]
  
 
* [[CDT/8.2 RC1 Testing]]
 
* [[CDT/8.2 RC1 Testing]]

Latest revision as of 16:04, 16 January 2020

Warning2.png
Note: The contents of this page is obsolete, but it may still contain some interesting tid-bits. The Manual Testing is now part of the [endgame] checklist

This is the main page for manual testing effort in the CDT project. Ideally the manual testing effort should help verify that a given release or build meets a certain quality standard. However, the CDT project relies on volunteers to contribute their time to make the project what it is. This page is designed to coordinate the efforts of volunteer testers to achieve maximum coverage and to assess the test completeness.

Test Instructions

If you wish to contribute to the test effort, edit the sign-up page and add your name to the sign up section. Under your name copy and paste the features which you would like to test. To perform the test, follow the link from the feature to the component's page where you'll find the description of the feature, which may include:

  • feature's details,
  • a link to a new and noteworthy entry for the feature,
  • a link to the user manual entry for the feature.

The component's page may also describe specific procedures which can be used to test the component's feature. However, it is not required that the given test procedure be used to test the feature. Any open source or commercial product build using the component being tested can be used to verify it. Of course the product has to be built using the version of the component which is being tested.

Any issues found during testing should be reported in bugzilla (see CDT/Bugs for more information on CDT bug process).

As your testing progresses, please update your test entries with a completion status. This status can be expressed as: [complete], [complete: no bugs] or [complete: bug 123456, bug 123457] and it can be added next to your name to affect all tests, or next to individual tests for a more detailed status.

Testing Coordination

Back to the top