Merge branch 'Test-Plan-&-Test-Cases' of https://github.com/algosup/2024-2025-project-3-quickest-path-team-1 into Test-Plan-&-Test-Cases

LucasMegnan · LucasMegnan · commit 1c967e0b660d · 2025-02-07T11:40:11.000+01:00
diff --git a/documents/TestCases.md b/documents/TestCases.md
@@ -14,8 +14,8 @@
 
 | Role | Name | Signature | Date |
 |------|------|-----------|------|
-| Project Manager      | [Alexis SANTOS](https://github.com/Mamoru-fr)                 |  |  |
-| Technical Lead       | [Grégory PAGNOUX](https://github.com/Gregory-Pagnoux)         |  |  |
+| Project Manager      | [Alexis SANTOS](https://github.com/Mamoru-fr)                 | ✅ | 02/07/2025|
+| Technical Lead       | [Grégory PAGNOUX](https://github.com/Gregory-Pagnoux)         | ✅ | 02/07/2025 |
 | Quality Assurance    | [Lucas MEGNAN](https://github.com/LucasMegnan)                | ✅ | 02/07/2025 |
 
 ---
@@ -41,7 +41,6 @@
   - [D. CSV files tests](#d-csv-files-tests-1)
   - [E. Output](#e-output-1)
 
-
 </details>
 
 # I. Introduction
@@ -73,7 +72,6 @@
 | **1.11** | Input a Int in the Localhost. | Verify if the program work correctly. | The program work correctly. | The program work correctly. | Tested on Mac and Windows. | High | ✅ |
 | **1.12** | Put more landmarks than nodes. | When we set up the program on the terminal, put 45 landmarks because we have 39 nodes. | Skipping X landmarks, maximum value has been reach + message. | Make the pre-processor successfully and put landmarks in addition on the first landmark. | Tested on Mac and Windows. | High | ❌ |
 
-
 ## B. Integrity & Connectivity tests
 
 | Test Case ID | Test Case Name | Test Case Description | Expected Result | Actual Result | Tested | Priority | Pass/Fail |
@@ -96,7 +94,7 @@
 | **4.01** | Compilation and running. | Verify the program laucnh well. | The program run and initialize. | The program run and initialize. | Tested on Mac and Windows. | High | ✅ |
 | **4.02** | Blanck space in the file .csv. | Space between the comma and a value in the test-blank-space.csv file. | return the file with the path found. | Return the file with the path found. | Tested on Mac and Windows. | Low | ✅ |
 | **4.03** | Input string distance in the file .csv. | Have a string distance value in the test-string-distance.csv file. | Send an ERROR message. | Send error 404 NO PATH FOUND. | Tested on Mac and Windows. | Low | ❌ |
-| **4.04** | Input float distance. | Have a float distance value in the test-float-distance.csv file. | Send an ERROR message. | It doesn’t take attention about the float and just take the int of the float (ex : 5.98, the program take 5). | Tested on Mac and Windows. | Medium | ❌ | 
+| **4.04** | Input float distance. | Have a float distance value in the test-float-distance.csv file. | Send an ERROR message. | It doesn’t take attention about the float and just take the int of the float (ex : 5.98, the program take 5). | Tested on Mac and Windows. | Medium | ❌ |
 | **4.05** | Signed number distance. | Have a signed distance value in the test-signed-number-distance.csv file. | Send an ERROR message. | The pre-processing block without send ERROR message. | Tested on Mac and Windows. | Medium | ❌ |
 | **4.06** | Input string node. | Have a string node value in the test-string-node.csv file. | Send an ERROR message. | **Mac**:  Message “terminating due to uncaught exception of type std::invalid_argument: stoi: no conversion”. **Windows**: Nothing, the program shutdown during the integrity check. | Tested on Mac and Windows. | Medium | ❌ |
 | **4.07** | Input float node. | Have a float node value in the test-float-node.csv file. | Send an ERROR message. | It doesn’t take a float and put it like an int. It return the path found. | Tested on Mac and Windows. | Low | ❌ |
@@ -168,4 +166,4 @@
 | **5.1** | Output XML. | Verify if the program send a XML file as an output. | Send a XML file. | It return a XML file. | Tested on Mac and Windows. | High | ✅ |
 | **5.2** | Output JSON. | Verify if the program send a JSON file as an output. | Send a JSON file. | It return a JSON file. | Tested on Mac and Windows. | High | ✅ |
 | **5.3** | Output another things. | Verify if the program send a another file as an output. | Send error 400 INVALID ACCEPT HEADER. | Send error 400 INVALID ACCEPT HEADER. | Tested on Mac and Windows. | Medium | ✅ |
-| **5.4** | Output comparaison. | Compare the result of XML and JSON. | Their are the same result. | The program return the same things. | Tested on Mac and Windows. | High | ✅ |
+| **5.4** | Output comparaison. | Compare the result of XML and JSON. | Their are the same result. | The program return the same things. | Tested on Mac and Windows. | High | ✅ |
diff --git a/documents/TestPlan.md b/documents/TestPlan.md
@@ -15,7 +15,7 @@
 | Role | Name | Signature | Date |
 |------|------|-----------|------|
 | Project Manager      | [Alexis SANTOS](https://github.com/Mamoru-fr)         |  |  |
-| Technical Lead       | [Grégory PAGNOUX](https://github.com/Gregory-Pagnoux) |  |  |
+| Technical Lead       | [Grégory PAGNOUX](https://github.com/Gregory-Pagnoux) | ✅ | 02/07/2025 |
 | Quality Assurance    | [Lucas MEGNAN](https://github.com/LucasMegnan)        | ✅ | 02/07/2025 |
 
 <details>
@@ -70,7 +70,7 @@ The system integration test of the quickest path must validate the following req
 - **Data Integrity**:
   - Verify that the file forms a Directed Acyclic Graph (DAG) and is free of loops.
   - Ensure that the graph is fully connected, meaning it is possible to navigate between any two landmarks.
-  - A utility to verify the integrity of the provided CSV file. 
+  - A utility to verify the integrity of the provided CSV file.
 - **Versatility**:
   - Demonstrating the ability to handle multiple formats (XML and JSON).
 
@@ -85,7 +85,7 @@ The scope is to **develop and validate a high-performance algorithm in C++** tha
 
 ## C. Product Overview
 
-Our software enginner aim to make **travel easier** with faster pathing using the language C++ and the software Visual Studio. 
+Our software enginner aim to make **travel easier** with faster pathing using the language C++ and the software Visual Studio.
 The users can use this to gain time and travel more effectively and easily across the United States.
 
 ## D. Definitions / Acronyms
@@ -104,7 +104,6 @@ The users can use this to gain time and travel more effectively and easily acros
 | **C++**      | a high-level, general-purpose programming language created by Danish computer scientist Bjarne Stroustrup. First released in 1985 as an extension of the C programming language, it has since expanded significantly over time; as of 1997, C++ has object-oriented, generic, and functional features, in addition to facilities for low-level memory manipulation for systems like microcomputers or to make operating systems like Linux or Windows. It is usually implemented as a compiled language, and many vendors provide C++ compilers, including the Free Software Foundation, LLVM, Microsoft, Intel, Embarcadero, Oracle, and IBM. | [Wikipedia C++](https://en.wikipedia.org/wiki/C%2B%2B) |
 | **Insomnia** | Insomnia is a powerful REST client that allows you to send HTTP requests and view responses from REST APIs. It is designed to be easy to use and helps developers debug and test their APIs more effectively. With Insomnia, you can create and save requests, organize them into workspaces, and share them with others. | [ProAbano Insomnia](https://docs.proabono.com/documentation/api-overview/what-is-insomnia-the-api-rest-client/) |
 
-
 ### 2. Acronyms
 
 | Acronyms | Definition |
@@ -134,7 +133,7 @@ The following people will be on the system integration test team:
 
 ## B. Team Reviews
 
-The following reviews will be conducted by the QA, and for the developement part the TL and SE will support the QA. 
+The following reviews will be conducted by the QA, and for the developement part the TL and SE will support the QA.
 Refer to the work schedule for the planned review dates.
 
 - Settlement review.
@@ -172,14 +171,16 @@ Our team members have different computer OS, which are Windows and MacOs, that g
 The tests will be run on the following environments:
 
 (1) Apple MacBook Air M3 2024
+
 - Apple M3
 - 16 GB
 - macOS Sequoia 15.1.1
 
-(1) Lenovo ThinkBook 14	
+(1) Lenovo ThinkBook 14
+
 - Intel Core i7-1065G7
-- 16 GB	
-- Windows 11 Pro 21H2	
+- 16 GB
+- Windows 11 Pro 21H2
 
 #### b. Network
 
@@ -268,7 +269,7 @@ Template of **PR**:
 ### 1. Test Cases
 
 For each requirement, system feature, or algorithm to be tested, the tester will execute a set of pre-defined test cases.
-Each test case will have a series of actions and expected results. 
+Each test case will have a series of actions and expected results.
 As each action is performed, the results are evaluated.
 If the observed results are equal to the expected results, a checkmark ✅ is placed in the “Pass/Fail” column.
 If the observed results are not equal to the expected results, a checkmark ❌ is placed in the “Pass/Fail” column.
@@ -305,33 +306,40 @@ order of testing will be followed:
 To pass the system integration test for the shortest path calculation software, the following criteria must be met:
 
 **Core Functionality**:
+
 - The system can calculate the quickest path between any two landmarks in a bidirectional positivly weighted graph within the performance goals.
 - The system exposes its functionality via a REST API with:
   - Correct handling of input landmark IDs.
   - Accurate travel time and ordered path output in XML and JSON formats.
   - The system supports bidirectional connections between landmarks as per the provided dataset.
 
 **Data Integrity**:
+
 - The system ensures graph validation, confirming that the dataset (.csv) forms a Directed Acyclic Graph (DAG) without loops.
 - After transforming the graph in an Undirected Cyclic Graph (UCG) perform a connectivity check to guarantee the graph allows navigation between any two landmarks.
 
 **Performance**:
+
 - The API must respond to all queries within one second on a typical laptop.
 - The system adheres to the 10% approximation rule, ensuring that the travel time does not exceed 10% of the shortest path duration.
 
 **Ease of Use**:
+
 - The REST API documentation is complete and user-friendly, enabling developers to integrate with minimal effort.
 - Error messages are informative and assist in troubleshooting input issues.
 
 **Security and Reliability**:
+
 - Adequate measures prevent unauthorized access to the system.
 - The system is resilient to failures, supporting recovery through documented procedures.
 
 **Integration and Extensibility**:
+
 - The system can integrate seamlessly with external tools or systems that utilize the REST API.
 - The design allows future enhancements without extensive rework.
 
 **Testing**:
+
 - All test cases in the provided suite for correctness, performance, and compliance with the 10% approximation rule are passed.
 - Validation tools confirm the integrity of the dataset without errors.
 
@@ -347,13 +355,13 @@ When all test cases have been executed, the test will be suspended and the resul
 
 ### 2. Abnormal Criteria
 
-As a general guideline, if the defect backlog continually increases over a ten days period, testing should be suspended. 
+As a general guideline, if the defect backlog continually increases over a ten days period, testing should be suspended.
 This will allow the developers time to fix existing defects without the pressure and confusion of new defects being added to the backlog.
 
-When a change is being migrated to the test environment, the system integration test team leader must be notified in advance to schedule a time for the move. 
+When a change is being migrated to the test environment, the system integration test team leader must be notified in advance to schedule a time for the move.
 After the move has been completed, a retest of previously tested functions should be performed.
 
-If a critical processing unit is found to have severe defects (as defined by the defect reporting process), testing should be suspended until the defects have been fixed. 
+If a critical processing unit is found to have severe defects (as defined by the defect reporting process), testing should be suspended until the defects have been fixed.
 When the fixed unit is moved back into the test environment, any previously performed tests that affect the unit should be performed again to ensure new defects were not created as a result of the fix.
 
 ## D. Defect Management
@@ -364,4 +372,4 @@ The test team will use the designated defect tracking system for reporting, main
 
 - **Medium**: Defects that result in incorrect or invalid information. Examples include miscalculation of payroll values or improper data validation, which may lead to data corruption.
 
-- **Low**: Defects that are cosmetic in nature and do not impact functionality. Examples include UI misalignment or minor deviations from design specifications.
+- **Low**: Defects that are cosmetic in nature and do not impact functionality. Examples include UI misalignment or minor deviations from design specifications.
