Project 2 - V&V SW Analysis II

  Abinaya Batch

1. 

Static Code Review Analysis: Static code review is a technique used to review and analyze source code without executing the code. The goal is to identify potential defects, code quality issues, security vulnerabilities, and adherence to coding standards.

Steps for Static Code Review Analysis:

1. Code Inspection: Open the "Testrain.c" file in a text editor or code review tool.

2. Readability and Formatting: Check for consistent indentation, appropriate naming conventions, and well-formatted code to improve readability.

3. Review Coding Standards: Ensure that the code follows the specified coding standards for the project or organization.

4. Code Structure: Check the overall code structure, including functions, classes, and control flow, to identify any potential issues.

5. Variables and Data Types: Review the usage of variables and data types to ensure correctness and appropriate usage.

6. Logic and Algorithm: Examine the logic and algorithms used in the code to verify their correctness and efficiency.

7. Error Handling: Check for proper error handling and exception handling mechanisms in the code.

8. Security: Identify potential security vulnerabilities, such as buffer overflows, input validation issues, and potential security risks.

9. Documentation: Review comments and documentation to ensure that the code is well-documented and easy to understand.

10. Code Reusability: Look for opportunities to improve code reusability through functions or modules.

11. Unit Testability: Assess whether the code can be easily unit tested for validation.

12. Review Results: Document the findings and any identified issues or improvements during the code review process.

2.

Integration Testing: Integration testing is a software testing technique that focuses on testing the interaction and integration between different components or modules of a software system. The objective is to verify that the integrated components work together correctly and produce the expected results.

Approach for Integration Testing with TBExtreme:

1. Identify Components: Determine all the .C files available in the folder location "C:**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0" that need to be integrated and tested together. These files represent the different components or modules.

2. Create Test Cases: Design test cases that cover different scenarios where the components interact. Consider inputs, outputs, data flow, and dependencies between components. Test cases should cover both positive and negative scenarios to validate the integration thoroughly.

3. Configure TBExtreme:

   • Launch TBExtreme and create a new test set for integration testing.
   • Select "Source" as "Multiple Files" to include multiple .C files in the test set.
   • Provide a name for the test set (e.g., "Integration_Test_Set").

4. Create Test Scenarios: Create test scenarios within the test set that define how the components interact with each other during integration.

5. Define Dependencies: Specify any system dependencies among the files. This information helps TBExtreme understand the interconnections and interactions between components.

6. Assign Test Cases: Assign the previously created test cases to the appropriate test scenarios.

7. Execute the Tests:

   • Run the test set using TBExtreme.
   • TBExtreme will execute the test cases, simulate the interactions between the components, and capture the results.

8. Review Test Results: After the test execution is complete, review the test results generated by TBExtreme to identify any issues or failures during integration.

Storing Test Cases as .tcf files: In TBExtreme, test cases can be stored as .tcf (Test Configuration File) files. The .tcf file contains the test configurations and scenarios that can be reused or shared with other team members.

To store test cases as .tcf files, I am following these steps mentioned below:

1. Create the test cases manually by defining the test scenarios and interactions between the components in TBExtreme.
2. Save the test cases as .tcf files using the "Save As" option within TBExtreme.