|
|
| (75 revisions intermèdies per 3 usuaris que no es mostren) |
| Línia 1: |
Línia 1: |
| [[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=
| |
| In a first time, we will use QA for major release in order to approved it.
| |
| | |
| =Draft/Ideas/Opinion/Requirements/Notes=
| |
| - there is a big lack of Functional Specification and Use Case. Developers and experimented user will be able to write such document. Need to identify them.
| |
| - Test case should usually not be written by developers neither people writting functional specs. will need to write use case or directly the test case.
| |
| - 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. This subtask will be Test Case.
| |
Revisió de 08:41, 15 set 2011
