Suborbital-Systems-Public/ReadySetGit
3
0
Fork 0
Code Pull Requests Packages Projects Releases Activity

GFM changes

Browse Source
This commit is contained in:
William Sandner
2018-08-14 23:32:43 +02:00
parent 6387d954be
commit 23485e2888
27 changed files with 139 additions and 929 deletions
Download Patch File Download Diff File Expand all files Collapse all files

111
QA-Plan.md
View File

@@ -1,27 +1,3 @@
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8"/>
<link type="image/png" href="assets/logo.png" rel="icon">
<title>ReadySet Markdown</title>
</head>
<script src="https://www.w3schools.com/lib/w3data.js"></script>
<body>
<topbar style="display:none;">
<item><a href="index.html">Overview</a></item>
<item><a href="plan.html">Project Plan</a></item>
<item><a href="index-all.html">Workflows</a></item>
<menu name="Themes"><item><a id="settheme"><b>Current</b></a></item></menu>
<toc></toc>
</topbar>
<xmp theme="readable" style="display:none;">
<!-- Markdown content here -->
# QA Plan
---
*TODO: For each release, update this file by filling in answers to the
questions. In cases where multiple answers are already written, delete
those answers that do not apply.*
@@ -39,9 +15,9 @@ those answers that do not apply.*
- ::Early access release (Controlled external access)
##### Attached Worksheets:
- QA plan > [Review meeting notes](review-meeting-notes.html)
- QA plan > [System test case suite](test-suite.html)
- QA plan > [System test runs](test-run-suite.html)
- QA plan > [Review meeting notes](Review-Meeting-Notes)
- QA plan > [System test case suite](Test-Suite)
- QA plan > [System test runs](Test-Run-Suite)
##### Related Documents:
- [Software Requirements Specification](SRS)
@@ -80,7 +56,7 @@ coordinate all the QA activities.
quotation marks and less-than signs) were entered and processed
properly, but not displayed properly. From now on, we must test
both validation and display of special characters.
- ::Large datasets can sometimes make our system fail if the space
- ::Large data sets can sometimes make our system fail if the space
used for temporary data is used up. Our test plans should
include more data volume tests.
@@ -106,7 +82,7 @@ correctness and robustness. We will do that with the following major
activities:
- ::using if-statements to test preconditions and assert statements
to test invariants and postconditions
to test invariants and post-conditions
- ::conducting frequent reviews
- ::performing automated unit and regression testing with JUnit
- ::carrying out structured manual system testing
@@ -118,33 +94,33 @@ activities:
that make sense for your project on this particular release.*
- ::Essential
- [Functionality > Correctness](Glossary-Standard-Terms#functionality_gt_correctness)
- [Functionality > Robustness](Glossary-Standard-Terms#functionality_gt_robustness)
- [Functionality > Correctness](Glossary-Standard-Terms#functionality--correctness)
- [Functionality > Robustness](Glossary-Standard-Terms#functionality--robustness)
- ::Expected
- [Functionality > Accuracy](Glossary-Standard-Terms#functionality_gt_accuracy)
- [Functionality > Compatibility](Glossary-Standard-Terms#functionality_gt_compatibility)
- [Functionality > Factual correctness](Glossary-Standard-Terms#functionality_gt_factual_correctness)
- [Usability > Understandability and Readability](Glossary-Standard-Terms#usability_gt_understandability_and_readability)
- [Usability > Learnability and Memorability](Glossary-Standard-Terms#usability_gt_learnability_and_memorability)
- [Usability > Task support](Glossary-Standard-Terms#usability_gt_task_support)
- [Usability > Efficiency](Glossary-Standard-Terms#usability_gt_efficiency)
- [Usability > Safety](Glossary-Standard-Terms#usability_gt_safety)
- [Usability > Consistency and Familiarity](Glossary-Standard-Terms#usability_gt_consistency_and_familiarity)
- [Usability > Subjective satisfaction](Glossary-Standard-Terms#usability_gt_subjective_satisfaction)
- [Functionality > Accuracy](Glossary-Standard-Terms#functionality--accuracy)
- [Functionality > Compatibility](Glossary-Standard-Terms#functionality--compatibility)
- [Functionality > Factual correctness](Glossary-Standard-Terms#functionality--factual-correctness)
- [Usability > Understandability and Readability](Glossary-Standard-Terms#usability--understandability-and-readability)
- [Usability > Learnability and Memorability](Glossary-Standard-Terms#usability--learnability-and-memorability)
- [Usability > Task support](Glossary-Standard-Terms#usability--task-support)
- [Usability > Efficiency](Glossary-Standard-Terms#usability--efficiency)
- [Usability > Safety](Glossary-Standard-Terms#usability--safety)
- [Usability > Consistency and Familiarity](Glossary-Standard-Terms#usability--consistency-and-familiarity)
- [Usability > Subjective satisfaction](Glossary-Standard-Terms#usability--subjective-satisfaction)
- [Security](Glossary-Standard-Terms#security)
- ::Desired
- [Reliability > Consistency under load](Glossary-Standard-Terms#reliability_gt_consistency_under_load)
- [Reliability > Consistency under concurrency](Glossary-Standard-Terms#reliability_gt_consistency_under_concurrency)
- [Reliability > Availability under load](Glossary-Standard-Terms#reliability_gt_availability_under_load)
- [Reliability > Longevity](Glossary-Standard-Terms#reliability_gt_longevity)
- [Reliability > Consistency under load](Glossary-Standard-Terms#reliability--consistency-under-load)
- [Reliability > Consistency under concurrency](Glossary-Standard-Terms#reliability--consistency-under-concurrency)
- [Reliability > Availability under load](Glossary-Standard-Terms#reliability--availability-under-load)
- [Reliability > Longevity](Glossary-Standard-Terms#reliability--longevity)
- [Efficiency](Glossary-Standard-Terms#efficiency)
- [Scalability](Glossary-Standard-Terms#scalability)
- [Scalability > Performance under load](Glossary-Standard-Terms#scalability_gt_performance_under_load)
- [Scalability > Large data volume](Glossary-Standard-Terms#scalability_gt_large_data_volume)
- [Scalability > Performance under load](Glossary-Standard-Terms#scalability--performance-under-load)
- [Scalability > Large data volume](Glossary-Standard-Terms#scalability--large-data-volume)
- [Operability](Glossary-Standard-Terms#operability)
- [Maintainability > Understandability](Glossary-Standard-Terms#maintainability_gt_understandability)
- [Maintainability > Evolvability](Glossary-Standard-Terms#maintainability_gt_evolvability)
- [Maintainability > Testability](Glossary-Standard-Terms#maintainability_gt_testability)
- [Maintainability > Understandability](Glossary-Standard-Terms#maintainability--understandability)
- [Maintainability > Evolvability](Glossary-Standard-Terms#maintainability--evolvability)
- [Maintainability > Testability](Glossary-Standard-Terms#maintainability--testability)
### QA Strategy
@@ -239,7 +215,7 @@ and tracked to completion.*
- ::Each week, identify reviewers and schedule review meetings
- ::Reviewers study the material individually for 2 hours
- ::Reviewers meet to inspect the material for 2 hours
- ::Place [review meeting notes](review-meeting-notes.html) in the
- ::Place [review meeting notes](Review-Meeting-Notes) in the
repository and track any issues identified in review meetings
3. Unit tests
@@ -256,7 +232,7 @@ and tracked to completion.*
- ::Update unit tests whenever requirements change
4. System tests
- ::Design and specify a detailed manual [test suite](test-suite.html).
- ::Design and specify a detailed manual [test suite](Test-Suite).
- ::Review the system test suite to make sure that every UI screen
and element is covered
- ::Execute system tests completely on each release candidate. These
@@ -274,7 +250,7 @@ and tracked to completion.*
issue tracker is available to all project members
[here](LINK-TO-ISSUE-TRACKER). The meaning of issue states,
priorities, and other attributes are defined in the
[SDM](sdm.html#issuetracking).
[SDM](SDM#issue-tracking).
### QA-Plan Checklist
@@ -285,8 +261,8 @@ and tracked to completion.*
this plan as needed.
::No, this plan leaves open several quality risks that have been noted
in the [Risk Management](Project-Plan#risks) section of the [Project
Plan](plan).
in the [Risk Management](Project-Plan#Risk-Management) section of the
[Project Plan](Project-Plan).
#### Have human resources been allocated to carry out the QA activities?
@@ -318,26 +294,5 @@ is welcome.
::No, some developers are not aware of the quality goals and planned
QA activities for this release. This is a risk that is noted in the
[Risk Management](Project-Plan#risks) section of the [Project Plan](Project-Plan).
<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
[Risk Management](Project-Plan#Risk-Management) section of the
[Project Plan](Project-Plan).