Test Developer Documentation - Standards, Definitions, Etc
As more developers participate in test development and more projects are added to the OpenStack umbrella, the lack of documented standards and project lore is beginning to impede the velocity of test development. Documenting the established processes, definitions, standards and expectations, similar to the developer documents will go a long way in helping to maintain/increase test development and become the place to point new test developers at for newbie questions.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Not
- Drafter:
- Rochelle Grober
- Direction:
- Needs approval
- Assignee:
- Rochelle Grober
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Matthew Treinish
Related branches
Related bugs
Sprints
Whiteboard
The QA group needs to better define "negative test".
In some test cases, "negative" has meant any test which tests for the absence of some feature or component.
In some tests, "negative" tests should test for cases where exceptions are expected to be thrown.
Clarification of the definition of "negative tests" in a QA wiki page will improve effectiveness and efficiency of the test developers.
Concepts:
Scope of QA driven testing (i.e. not unit)
Definitions:
Tests:
positive
negative
integration
scenario
stress
unit (link to def?)
How to:
Links to developer documents on setup, gotchas, etc
Standards:
Naming
Reporting results
Coding
References:
Other guides, wiki pages, etc.:
Link to existing pages documenting test directory structures in Git
Link to other existing docs that aid in testing
Resources
