|
|
| (59 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| {{stub}}[[Category:Quality Assurance]] | | {{Moved_to_dev_docs}} |
| | |
| =What is QA=
| |
| Few documents related to QA/Testing on Wikipedia: [http://en.wikipedia.org/wiki/Software_quality_assurance], [http://en.wikipedia.org/wiki/Software_testing]
| |
| | |
| =Introduction=
| |
| The document will set up the Moodle QA lines. Any participation is welcome. Please use the tab "page comments" in order to participate to the writting of this page. A good Moodle QA will be a great benefit for Moodle but also for any company using Moodle.
| |
| | |
| =QA for Moodle=
| |
| Main objectif: is a major release ok for release?
| |
| | |
| A major release is ok when (TBD):
| |
| * critical bug number < 5%
| |
| * major bug number < 20%
| |
| * new functionalities has been implemented
| |
| | |
| =Need to be identified=
| |
| QA Cost (in persons/hours) for:
| |
| * writting test cases (first time, then updated)
| |
| * preparing the QA cycle (update test case, get a new QA system ready for testing, update test data)
| |
| * delivered a test data package?
| |
| * running test cases
| |
| | |
| When a QA cycle should be run
| |
| | |
| Who can write test cases
| |
| | |
| What Function specs/Use have we got
| |
| | |
| Who can run test cases
| |
| | |
| =Draft/Ideas/Opinion/Requirements/Notes=
| |
| * There is a lack of Functional Specification and Use Case. Only Developers and experimented user would be able to write such document.
| |
| * Test case should usually not be written by developers neither people writting functional specs. Probably cannot follow this rule. The main is reason is that test case writer usually uses Use Case (and functional specs) in order to write test case. I don't think that such document are going to be written. So Developers and experimented user will have to write the test cases.
| |
| * We need to make a clear statement of the Moodle docs in order to make a difference between: User Manuals, Function Specifications, Technical Specifications, Requirements, ... and many mixed document. (The moodle docs are a powerful resource of information, however at the current time Google is your best friend in order to find information.)
| |
| * use JIRA tracking system: we will use Jira as Test Case Managment system. Jira as not been developed for Test Case Management system but can be use for manage simple QA environment. The main reason to use Jira is to use a software that the community is familiar with.
| |
| * JIRA as a Test Case Management System: We'll create a main issue containing thousand of sub-tasks. These subtasks will be Test Case.
| |
| * study Quality Assurance into open source world, how does the other project manage their QA department?
| |
| * Moodle doesn't have deadline. It is released when it will be ready. But avoid no-end QA phase.
| |
| * experimented user can test Moodle.
| |
| * some people/company using Moodle probably have already written test plans, test cases, maybe use case.
| |
| * need documentation on how to write a test case
| |
