Update QA guideline
This commit is contained in:
parent
b6a2c50f83
commit
788d7c7088
@ -2,10 +2,4 @@
|
|||||||
|
|
||||||
A faulty application will cost a considerable amount of time, money and reputation. Having effective QA management ensures that developed software projects maintain quality, efficiency, consistency, meet client’s requirements, and are finished with minimal flaws and bugs. Without it, software development could be quite unreliable.
|
A faulty application will cost a considerable amount of time, money and reputation. Having effective QA management ensures that developed software projects maintain quality, efficiency, consistency, meet client’s requirements, and are finished with minimal flaws and bugs. Without it, software development could be quite unreliable.
|
||||||
|
|
||||||
While having a high quality product is crucial, it’s very important to have the product within the specified deadline. In order to achieve this, following steps are the best practices of how to improve the software testing process and to increase the quality of your software products within the deadline.
|
While having a high quality product is crucial, it’s very important to have the product within the specified deadline. In order to achieve this, following steps are the best practices of how to improve the software testing process and to increase the quality of your software products within the deadline.
|
||||||
|
|
||||||
1. [Test Planning](03-Test Planning.md)
|
|
||||||
2. [Test Design](04-Test Design.md)
|
|
||||||
3. [Test Execution](06-Test Execution.md)
|
|
||||||
4. [Defect Management](07-Defect Management.md)
|
|
||||||
|
|
||||||
Loading…
Reference in New Issue
Block a user