Merge branch 'dev' into fixing-typos

.github/CODEOWNERS

@@ -1,2 +1,5 @@
 /.github/ @ditkrg/devops
 /kubernetes/ @ditkrg/devops
+
+/.dockerignore @ditkrg/devops
+/Dockerfile @ditkrg/devops

.github/workflows/deploy-base.yaml

@@ -32,9 +32,9 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Kubectl tool installer
-        uses: Azure/setup-kubectl@v1
+        uses: Azure/setup-kubectl@v3
 
-      - uses: azure/k8s-set-context@v1
+      - uses: azure/k8s-set-context@v3
         with:
           method: kubeconfig
           kubeconfig: ${{ secrets.KUBECONFIG }}

.github/workflows/tests-base.yaml

@@ -24,7 +24,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Kubectl tool installer
-        uses: Azure/setup-kubectl@v1
+        uses: Azure/setup-kubectl@v3
 
       - name: Setup Kustomize
         uses: imranismail/setup-kustomize@v1

docs/Quality Assurance/01-Guidelines for Quality Assurance.md

@@ -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.
 
-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)
- 

docs/Quality Assurance/01-Quality Assurance Phase.md

@@ -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.

docs/Quality Assurance/04-Test Case Design.md

@@ -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).

docs/Quality Assurance/06-Defect Management.md

@@ -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).

docs/intro.md

@@ -1,6 +1,6 @@
 # Introduction
 
-The Department of Information Technology uses an agile methodology for developing and digitizing government services. The process for developing a digital service consists of a cycle of three different phases:
+The Department of Information Technology uses an agile methodology for developing and digitizing government services. The process for developing a digital service consists of a cycle of four different phases:
 
 ## Discovery phase
 
@@ -13,6 +13,14 @@ The first step of the process is to understand what is the service, what are the
 
 When enough requirements are documented after the discovery phase, the Development team starts developing the system with the latest technologies and standards. Additionally, the DevOps team starts preparing the development environment, and builds the CI/CD pipelines for the project. In this phase the system goes through an iterative development process until the software is ready for production. At the end of each iteration the Business Intelligence and Requirement Analysis team checks if all the requirements are met, then the Quality Assurance team will start testing the software before it is released.
 
+# 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.
+
 ## Production phase
 
 After the software is developed and tested, it is shipped to production. Even in production the software is still monitored for any error or bugs for further improvement. If there are any changes that need to be made, the cycle goes back to the discovery phase where the Business Intelligence and Requirements Analysis team starts researching the changes. Furthermore, handover details of the changes to the Development team, and after changes have been implemented shipping it back to production again.