Project 2 - V&V SW Analysis II
|
Static Analysis: 1. Perform Static Code Review Analysis for “C:\**\LDRA_workarea\Examples\C_tbrun_examples\Ggrocers.c” (Single .c file), modify the Code to remove violations and make compliant to MISRA: C 2012 & CERT standards.
Output/Reports: Code review report compliant to MISRA: C 2012 & CERT standards (2 html reports with no violations) Dynamic Analysis – White box testing: 2. Perform Unit testing for “C:\**\LDRA_workarea\Examples\C_tbrun_examples\Ggrocers.c” (Loading Single file)
Output/Reports: Dynamic Code coverage report, Regression report and Testmanager report. (3 html reports with 100% statement, Branch/Decision and MC/DC coverage and one .tcf file ) 3. Perform Unit testing for “C:\**\LDRA_workarea\Examples\ C_testbed_examples\Advanced\Big_gear.c” (Loading Single file)
Output/Reports: Dynamic Code coverage report, Regression report and Testmanager report. (3 html reports with 100% statement, Branch/Decision and MC/DC coverage and one .tcf file) 4. Perform Integration testing for “C:\**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0\ Cashregister.tcf” (Multiple files/Set creation using tcf file or manual way)
Output/Reports: Dynamic Code coverage report, Regression report and Testmanager report. (3 html reports with 100% statement, Branch/Decision and MC/DC coverage and one .tcf file) |
Static analysis: to make and produce compliant reports as per MISRA & CERT standards (with no violations or with deviations). Unit testing: To create & execute test cases and to get coverage report with 100% statement, Branch/Decision and MC/DC coverage. (Project Marks to be given based on coverage percentage achieved) |
Your Answers
|
Analysis: 1. Perform Static Code Review Analysis for “C:\**\LDRA_workarea\Examples\C_tbrun_examples\Ggrocers.c” (Single .c file), modify the Code to remove violations and make compliant to MISRA: C 2012 & CERT standards.
|
Static code analysis is a method of debugging by examining source code before a program is run. It's done by analyzing a set of code against a set (or multiple sets) of coding rules. Static code analysis and static analysis are often used interchangeably, along with source code analysis.
We are going to open TBvision, open the Ggrocer.c file, and set the standard as Cert c.
after setting to Cert c standard we are going to take summary report
According to the summary report, the violations are found :
.
The violations are displayed.
|
Static Analysis: 1. Perform Static Code Review Analysis for “C:\**\LDRA_workarea\Examples\C_tbrun_examples\Ggrocers.c” (Single .c file), modify the Code to remove violations and make compliant to MISRA: C 2012 & CERT standards.
Output/Reports: Code review report compliant to MISRA: C 2012 & CERT standards (2 html reports with no violations) Dynamic Analysis – White box testing: 2. Perform Unit testing for “C:\**\LDRA_workarea\Examples\C_tbrun_examples\Ggrocers.c” (Loading Single file)
Output/Reports: Dynamic Code coverage report, Regression report and Testmanager report. (3 html reports with 100% statement, Branch/Decision and MC/DC coverage and one .tcf file ) |
- Black Box Testing is a software testing method in which the internal structure/design/implementation of the item being tested is not known to the tester. Only the external design and structure are tested.
- White Box Testing is a software testing method in which the internal structure/design/implementation of the item being tested is known to the tester. Implementation and impact of the code are tested.
The test case are save in.tcf file
From the above figure, i have white box testing for the Ggrocer.c file and got the coverages and test manager report.
3. Perform Unit testing for “C:\**\LDRA_workarea\Examples\ C_testbed_examples\Advanced\Big_gear.c” (Loading Single file)
- Create the test cases manually as well as automatically using TBExtreme and execute the test cases to get 100% statement, Branch/Decision and MC/DC coverage.
- Generate Dynamic Code coverage report, Regression report and Testmanager report.
- Save the test cases as .tcf file.
The test case are save in.tcf file
From the above figure, i have white box testing for the Ggrocer.c file and got the coverages and test manager report.
4. Perform Integration testing for “C:\**\LDRA_workarea\Examples\Toolsuite\Cashregister_6.0\ Cashregister.tcf” (Multiple files/Set creation using tcf file or manual way)
- Create the test cases manually as well as automatically using TBExtreme and execute the test cases to get 100% statement, Branch/Decision and MC/DC coverage.
- Generate Dynamic Code coverage report, Regression report and Testmanager report.
- Save the test cases as .tcf file.
Output/Reports: Dynamic Code coverage report, Regression report and Testmanager report. (3 html reports with 100% statement, Branch/Decision and MC/DC coverage and one .tcf file)
Integration testing is a type of testing meant to check the combinations of different units, their interactions, the way subsystems unite into one common system, and code compliance with the requirements. For example, when we check login and sign up features in an e-commerce app, we view them as separate units.
Software Engineering defines variety of strategies to execute Integration testing, viz.
- Big Bang Approach :
- Incremental Approach: which is further divided into the following
- Top-Down Approach
- Bottom-Up Approach
- Sandwich Approach – Combination of Top-Down and Bottom-Up
First, we are going to use the LDRA launcher
create a file as demo
.
intergration is done completely and dynamic coverage report is generated.
With integration testing, you can find the defects in a structure while interactions happen between modules. So, as a tester, if you would like to have a streamlined development process, where implementing new functionality into production is easy, you should perform integration testing.