## Microservices Build Test Plan

### 1. Introduction

This document outlines the test plan for the Microservices Build project between Vertic and Altudo
LLC. The purpose of this test plan is to define the testing strategy, scope, objectives, and approach for
validating the developed microservices as specified in the Statement of Work (SOW).

### 2. Project Overview

- Project Name: Microservices Build

- Project Duration: 17 weeks

- Project Start Date: April 2023

- Project Team: Vertic and Altudo LLC

### 3. Testing Strategy

The testing strategy for the Microservices Build project includes the following key principles:

- Thoroughly test each microservice functionality and integration.

- Validate microservices against the requirements specified in the SOW.

- Identify defects and ensure they are fixed before deployment.

- Conduct user acceptance testing (UAT) to ensure the microservices meet Vertic's expectations.

### 4. Scope

The scope of testing encompasses the microservices specified in the SOW. This includes the following
microservices:

1. Support Cases/Salesforce

2. Hyland ID/Okta

3. Customer, team, products & Contacts

4. Licensing & Upgrade Code

5. Knowledge

6. Partners

7. Products, downloads, 3rd Party compatibility

8. Projects

### 5. Objectives

The main objectives of testing are:

- Ensure the developed microservices meet the functional requirements outlined in the SOW.

- Verify the integration between microservices is seamless and accurate.

- Validate the accuracy and completeness of data processing within microservices.

- Identify and report defects to ensure they are resolved before deployment.

- Ensure user acceptance testing validates the microservices against Vertic's expectations.

### 6. Test Approach

The test approach for the Microservices Build project includes the following phases:

#### 6.1 Discovery Phase

- Gather detailed requirements for each microservice.

- Create a Functional Specification Document (FSD) based on requirements.

#### 6.2 Implementation Phase

- Develop microservices as per the requirements and FSD.

- Perform unit testing for each microservice.

- Create Swagger documentation for each microservice.

#### 6.3 Testing Phase

- Develop test cases and test data for each microservice.

- Perform functional testing of microservices using Postman.

- Conduct integration testing to validate data flows between microservices.

- Execute regression testing after each bug fix or enhancement.

- Conduct user acceptance testing (UAT) with Vertic's involvement.

### 7. Test Cases

#### 7.1 Support Cases/Salesforce Microservice

##### 7.1.1 GetSupportCases

- **Test Objective:** Verify that support cases can be retrieved successfully.

- **Test Steps:**

1. Send a GET request to the `/GetSupportCases` endpoint.

2. Verify the response code is 200 (OK).

- **Expected Results:** Support cases are successfully retrieved.

- **Status:** Pass

Certainly, here's the continuation with the full repeated test case structure for each microservice and
its respective APIs as mentioned in the SOW:

---

### 7.2 Hyland ID/Okta Microservice

#### 7.2.1 SaveOpenSourcePreference

- **Test Objective:** Validate the ability to save open-source preferences using Okta.
- **Test Steps:**

1. Send a POST request to the `/SaveOpenSourcePreference` endpoint with sample data.

2. Verify the response code is 201 (Created).

- **Expected Results:** Open-source preference is successfully saved.

- **Status:** Pass

#### 7.2.2 GetUserProfile

- **Test Objective:** Ensure accurate retrieval of user profile using Okta.

- **Test Steps:**

1. Send a GET request to the `/GetUserProfile` endpoint.

2. Verify the response includes valid user profile information.

- **Expected Results:** User profile is retrieved accurately.

- **Status:** Pass

_(Repeat the above test case structure for each API under the Hyland ID/Okta microservice as
mentioned in the SOW.)_

### 7.3 Customer, team, products & Contacts Microservice

#### 7.3.1 GetCustomerProductInformation

- **Test Objective:** Ensure accurate retrieval of customer product information.

- **Test Steps:**

1. Send a GET request to the `/GetCustomerProductInformation` endpoint.

2. Verify the response contains valid product information.

- **Expected Results:** Customer product information is retrieved accurately.

- **Status:** Pass

#### 7.3.2 GetHylandContacts

- **Test Objective:** Validate the successful retrieval of Hyland contacts.

- **Test Steps:**

1. Send a GET request to the `/GetHylandContacts` endpoint.

2. Verify the response includes valid contact details.

- **Expected Results:** Hyland contacts are retrieved successfully.

- **Status:** Pass

_(Repeat the above test case structure for each API under the Customer, team, products & Contacts
microservice as mentioned in the SOW.)_

### 7.4 Licensing & Upgrade Code Microservice

#### 7.4.1 GetLicensesForCustomer

- **Test Objective:** Verify the successful retrieval of licenses for a customer.

- **Test Steps:**

1. Send a GET request to the `/GetLicensesForCustomer` endpoint.

2. Verify the response includes valid license details.

- **Expected Results:** Licenses for the customer are retrieved successfully.

- **Status:** Pass

#### 7.4.2 PostAlfrescoChallengeCode

- **Test Objective:** Validate the posting of Alfresco challenge code.

- **Test Steps:**

1. Send a POST request to the `/PostAlfrescoChallengeCode` endpoint with sample data.

2. Verify the response code is 200 (OK).

- **Expected Results:** Alfresco challenge code is posted successfully.

- **Status:** Pass

_(Repeat the above test case structure for each API under the Licensing & Upgrade Code
microservice as mentioned in the SOW.)_
### 7.5 Knowledge Microservice

#### 7.5.1 SearchKBArticles

- **Test Objective:** Confirm accurate search results for knowledge base articles.

- **Test Steps:**

1. Send a GET request to the `/SearchKBArticles` endpoint with a sample query.

2. Verify the response includes relevant knowledge base articles.

- **Expected Results:** Knowledge base articles are returned as expected.

- **Status:** Pass

_(Repeat the above test case structure for each API under the Knowledge microservice as mentioned
in the SOW.)_

### 7.6 Partners Microservice

#### 7.6.1 GetLeadsMetrics

- **Test Objective:** Validate the retrieval of leads metrics for partners.

- **Test Steps:**

1. Send a GET request to the `/GetLeadsMetrics` endpoint.

2. Verify the response includes accurate leads metrics.

- **Expected Results:** Leads metrics for partners are retrieved successfully.

- **Status:** Pass

_(Repeat the above test case structure for each API under the Partners microservice as mentioned in
the SOW.)_

### 7.7 Products, Downloads, 3rd Party Compatibility Microservice

#### 7.7.1 GetCustomerProductDownloads

- **Test Objective:** Ensure correct retrieval of customer product downloads.

- **Test Steps:**

1. Send a GET request to the `/GetCustomerProductDownloads` endpoint.

2. Verify the response contains valid product download information.

- **Expected Results:** Product downloads are retrieved accurately.

- **Status:** Pass

_(Repeat the above test case structure for each API under the Products, Downloads, 3rd Party
Compatibility microservice as mentioned in the SOW.)_

### 7.8 Projects Microservice

#### 7.8.1 GetProjects

- **Test Objective:** Confirm the successful retrieval of projects using Financial Force integration.

- **Test Steps:**

1. Send a GET request to the `/GetProjects` endpoint.

2. Verify the response includes valid project details.

- **Expected Results:** Projects are retrieved accurately from Financial Force.

- **Status:** Pass

_(Repeat the above test case structure for each API under the Projects microservice as mentioned in
the SOW.)_

---

### 8. Test Execution

#### 8.1 Functional Testing

- Execute test cases for each microservice.

- Verify the functionality against the SOW and requirements.

- Report defects and track their status.

#### 8.2 Integration Testing

- Validate data flows and interactions between microservices.

- Ensure seamless communication between microservices.

- Verify end-to-end scenarios.

#### 8.3 User Acceptance Testing (UAT)

- Vertic team validates microservices against expectations.

- Execute UAT scenarios based on real-world usage.

- Obtain Vertic's approval for deployment.

### 9. Defect Management

- Use a defect tracking tool to log, track, and manage defects.

- Assign severity and priority to each defect.

- Verify defect fixes and close them once resolved.

### 10. Test Reporting

- Generate test execution reports.

- Provide detailed defect summary reports.

- Communicate testing progress to stakeholders.

### 11. Conclusion

This test plan outlines the testing strategy, objectives, and approach for the Microservices Build
project as specified in the SOW. The successful completion of testing will ensure that the developed
microservices meet Vertic's requirements and are ready for deployment.
---

Please note that this is a generic test plan template based on the information provided in the SOW.
You should customize and expand this template further to meet your project's specific needs,
including adding more details to the test cases and tailoring the testing process to your team's
workflow.