Project 2 - V&V SW Analysis II

1.Perform Static Code Review Analysis for “C:\**\LDRA_workarea\Examples\C_Testbed_examples\Testrain\Testrain.c” Generate Code review report and upload them.

Performing a static code review analysis involves examining the source code of a software program without executing it. Here are the general procedure steps to perform a static code review analysis for the specified file, "C:**\LDRA_workarea\Examples\C_Testbed_examples\Testrain\Testrain.c," and generate a code review report:

1. Set up the analysis environment:

   • Install a static code analysis tool such as SonarQube, CodeSonar, or Coverity.
   • Configure the tool to analyze C programming language.
   • Ensure that the necessary compilers and dependencies are installed.

2. Import the project:

   • Launch the static code analysis tool.
   • Create a new project or import an existing one.
   • Specify the location of the "Testrain.c" file.

3. Configure analysis settings:

   • Adjust the analysis settings according to your project requirements.
   • Specify any additional rules, coding standards, or quality metrics to enforce.
   • Configure any custom analysis options specific to your project.

4. Run the analysis:

   • Start the static code analysis process.
   • The tool will parse and analyze the source code for potential issues, vulnerabilities, or violations of coding standards.
   • The analysis may take some time depending on the size and complexity of the project.

5. Review the analysis results:

   • Once the analysis is completed, review the generated reports.
   • The tool will provide a list of identified issues, code smells, and potential vulnerabilities.
   • Examine each reported item, understand the context, and evaluate its severity.

6. Generate a code review report:

   • Extract the relevant findings from the analysis results.
   • Compile a comprehensive code review report that includes a summary, detailed explanations of issues, and recommendations for improvements.
   • Include code snippets, line numbers, and any additional information that helps to understand the reported issues.
   • Organize the report in a clear and readable format.

7. Upload the code review report:

   • Choose a suitable platform for sharing the code review report, such as a project management tool, version control system, or document sharing platform.
   • Create a new document or add the code review report to an existing location.
   • Upload the report, ensuring that it is accessible to the relevant stakeholders.

2.Perform Integration testing by including all the .C files available in the folder locationC:\**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0\ **         

A)Create the test cases manually as well as automatically using TBExtreme and upload the reports.       

Performing integration testing for all the .C files available in the folder location "C:**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0" involves testing the interactions and behavior of the components when they are integrated together. Here are the procedure steps to perform integration testing manually and automatically using TBExtreme and upload the reports:

1. Set up the integration testing environment:

   • Install the required tools and dependencies.
   • Ensure that the necessary compilers and build systems are available.

2. Manually create test cases:

   • Identify the functionalities and interactions of the components in the Cashregister_6.0 project.
   • Create test cases that cover different scenarios and combinations of components.
   • Determine the input data, expected output, and any specific conditions or constraints for each test case.
   • Document the test cases in a suitable format, such as a spreadsheet or test management tool.

3. Automatically create test cases using TBExtreme:

   • Launch TBExtreme, a test automation tool.
   • Create a new project or open an existing one.
   • Configure the project settings and environment variables as required.

4. Import the .C files:

   • Add all the .C files available in the folder location "C:**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0" to the integration testing project in TBExtreme.
   • Ensure that the file dependencies and include paths are correctly set up.

5. Create test suites and test cases:

   • Define test suites that group related test cases together.
   • Within each test suite, create test cases that cover different integration scenarios.
   • Specify the input data, expected output, and any specific conditions or constraints for each test case.
   • Utilize TBExtreme's features for generating test data or capturing test inputs and outputs.

6. Run the integration tests:

   • Start the integration test execution in TBExtreme.
   • TBExtreme will execute the test cases and record the results.
   • Monitor the execution progress and ensure that all test cases are executed.

7. Analyze the test results:

   • Review the test execution reports generated by TBExtreme.
   • Analyze the pass/fail status, test coverage, and any captured logs or artifacts.
   • Identify any issues or failures and investigate their root causes.

8. Generate test reports:

   • Compile a comprehensive integration test report that includes a summary, detailed test case descriptions, and the results.
   • Include relevant information such as test coverage, test duration, and any defects or issues found during testing.
   • Organize the report in a clear and readable format.

9. Upload the test reports:

   • Choose a suitable platform for sharing the test reports, such as a project management tool, version control system, or document sharing platform.
   • Create a new document or add the test report to an existing location.
   • Upload the report, ensuring that it is accessible to the relevant stakeholders.

                                                                             

B)store the test cases as .tcf file.  Upload the location image where the .tcf file is stored.

 

To perform integration testing for all the .C files available in the folder location "C:**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0", and store the test cases as a .tcf file, follow these procedure steps:

1. Open a text editor or an integrated development environment (IDE) that supports creating and saving files.

2. Create a new file and name it with a .tcf extension (e.g., "integration_testcases.tcf").

3. Write or copy-paste your integration test cases into the .tcf file, ensuring that each test case is properly formatted and organized.

4. Save the file with the .tcf extension in the desired folder location: "C:**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0".

5. Once you have saved the .tcf file, you can provide the location image by following these steps: a. Open the file explorer on your computer. b. Navigate to the folder location "C:**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0". c. Take a screenshot of the file explorer window, showing the folder location and the .tcf file. d. Save the screenshot image to your local machine. e. Upload the location image to a suitable image hosting platform or file-sharing service. f. Share the image's URL or link in this chat to indicate the location where the .tcf file is stored.

Declaration:

Because of compiler problem whatever i expected outcomes are not getting. and also for all questions the results are not showing