Project 2 - V&V SW Analysis II

• an intern didn't know that the piece of code he/she created introduced a security vulnerability,
• a developer was multi-tasking due to a short deadline, stress and high pressure at work and forgot to check the code for security vulnerabilities,
• a senior developer was performing a code review after exhausting day at work and oversaw a security vulnerability that was introduced as part of a pull request,

and the list goes on…Therefore it's important to have other security tools in place, in addition to manual code review, that can help us analyze the code, detect potentially insecure code and alert us about it BEFORE the code is merged to master. That's where static code analysis (aka. source code analysis) comes in.

• an intern didn't know that the piece of code he/she created introduced a security vulnerability,
• a developer was multi-tasking due to a short deadline, stress and high pressure at work and forgot to check the code for security vulnerabilities,
• a senior developer was performing a code review after exhausting day at work and oversaw a security vulnerability that was introduced as part of a pull request,

and the list goes on…Therefore it's important to have other security tools in place, in addition to manual code review, that can help us analyze the code, detect potentially insecure code and alert us about it BEFORE the code is merged to master. That's where static code analysis (aka. source code analysis) comes in.

2.

• 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)