ditkrg/dit-digital-service-manual
5
0
Fork 0
Code Issues Pull Requests Packages Projects 1 Releases Wiki Activity

Update intro

Browse Source
This commit is contained in:
LANA-DIT
2022-10-19 12:44:52 +03:00
parent 788d7c7088
commit 27dc94acd8
8 changed files with 11 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
docs/Quality Assurance/02-Guidelines for Quality Assurance.md → docs/Quality Assurance/01-Guidelines for Quality Assurance.md
View File

7
docs/Quality Assurance/01-Quality Assurance Phase.md
View File

@@ -1,7 +0,0 @@
# Quality Assurance Phase
Once the development of the software is complete in each sprint, it will be handed over to the Quality Assurance Team along with the technical documentations prepared in the Discovery Phase.
Based on the provided technical documentations, the QA team will plan and test the system properly. When there is a bug or an improvement needed, it will be reported to the development team. Upon a fix by the Development Team, it will be re-tested by the QA team again. This cycle will continue until the software is stable to ensure delivering high-quality services that match user needs and stockholders expectations.
It is highly recommended to involve the QA Team from the early stages of the Software Development Life Cycle (SDLC). Integrating QA practices at the beginning will result in a well-planned and executed project that successfully delivers high value to the stockholders.

0
docs/Quality Assurance/03-Test Planning.md → docs/Quality Assurance/02-Test Planning.md
View File

0
docs/Quality Assurance/04-Test Design.md → docs/Quality Assurance/03-Test Design.md
View File

2
docs/Quality Assurance/05-Test Case Design.md → docs/Quality Assurance/04-Test Case Design.md
View File

@@ -29,4 +29,4 @@ During test execution time, the tester will check expected results against actua
That apart your test case -may have a field like, Pre – Condition which specifies things that must be in place before the test can run. For our test case, a pre-condition would be to have the application installed to have access to the Application under test. A test case may also include Post – Conditions which specifies anything that applies after the test case completes. For our test case, a post-condition would be time & date of login is stored in the database
By the end of the test case execution phase, all the executed test cases should be recorded in a template like [this](https://govkrd.b-cdn.net/Digital%20Service%20Manual/Test%20Case%20Design%20Template.docx).
By the end of the test case execution phase, all the executed test cases should be recorded in a template like [this](https://govkrd.b-cdn.net/Digital%20Service%20Manual/Test%20Case%20Design%20Template.xlsx).

0
docs/Quality Assurance/06-Test Execution.md → docs/Quality Assurance/05-Test Execution.md
View File

2
docs/Quality Assurance/07-Defect Management.md → docs/Quality Assurance/06-Defect Management.md
View File

@@ -8,4 +8,4 @@ Defect Management is a method for identifying and resolving defects. The steps o
4. QA team verification
5. Defect Closure
All the defects that are found in the testing phase should be recorded in a template like [this](https://govkrd.b-cdn.net/Digital%20Service%20Manual/Defect%20Management%20Template%20Template.docx).
All the defects that are found in the testing phase should be recorded in a template like [this](https://govkrd.b-cdn.net/Digital%20Service%20Manual/Defect%20Management%20Template.xlsx).