Presentation of Testing results of SRCP softwares & detailed result written on Master test specification.

1. MASTER TEST SPECIFICATION FOR SIMPLE RAILROAD COMMAND PROTOCOL(SRCP) 28 JUNE 2010 Tester, Ankit Singh Masters High Integrity System University of Applied Sciences Frankfurt am Main

3. PROJECT SCHEDULE

5. TEST METRICS USED Test metric Definition Purpose How to calculate Defect severity The severity level of a defect indicates the potential business impact for the end user (business impact = effect on the end user x frequency of occurrence). Provides indications about the quality of the product under test. High-severity defects means low product quality, and vice versa. At the end of this phase, this information is useful to make the release decision based on the number of defects and their severity levels. Every defect has severity levels attached to it. Broadly, these are Critical, Serious, Medium and Low. Test coverage Defined as the extent to which testing covers the products complete functionality. This metric is an indication of the completeness of the testing. It does not indicate anything about the effectiveness of the testing. This can be used as a criterion to stop testing. Coverage could be with respect to requirements, functional topic list, business flows, use cases, etc. It can be calculated based on the number of items that were covered vs. the total number of items.

7. WRONG TEST SPECIFICATION (BLACK BOX TESTING) Test Case ID.No Test Area Command Expected Output Behavior Description Severity Level 3_1 Command set ConnEctionMode Srcp Command 410 ERROR unknown command Fail : <TimeStamp>202 OK CONNECTIONMODE Low 3_2 Feedback SET 1 FB 0x111111 0 100 INFO 1 FB 0x111111 0 Fail: <TimeStamp> 422 ERROR unsupported device group Critical 3_3 Session GET 0 SESSION 2 100 INFO 0 SESSION 2 Fail: <TimeStamp> 422 ERROR unsupported device group Critical 3_4 Server RESET 0 SERVER 101 INFO 0 SERVER Fail : <TimeStamp> 423 ERROR unsupported operation Crititcal 3_5 Time TERM 0 TIME 102 INFO 0 TIME Fail: <TimeStamp> 422 ERROR unsupported device group Critical

9. WHITE BOX TESTING REPORT SAFE CODING GUIDELINES Function Bug Suggestion enqueueInfoFB 1000, Message length hardcoded Should be passed any specified message, and calculate size dynamically queue_reset_fb usleep not checked for incorrect result check the result returned by usleep() infoFB msg overflow can occur, so message length should be dynamically checked Check for the overflow