Assignment - 1. Why we need Test plan and what are the elements that it identifies?

Size: px

Start display at page:

Download "Assignment - 1. Why we need Test plan and what are the elements that it identifies?"

Beverley Dawson
5 years ago
Views:

1 Assignment - 1 Why we need Test plan and what are the elements that it identifies? The duration of the assignment is 3 Hours. Document contains fallowing points Need test plans Test plan elements 5 Marks are awarded for the need test plan 5 Marks are awarded for test plan elements identification

2 Assignment - 2 Write test strategy for the below set of requirements: An Embedded Unit Instrument product, the software requirements are as per below: Requirements Specification for Embedded Unit Instrument Overview: The EUI implements the following main functions: INIT: Initialization MAINTENANCE: Maintenance mode management BIT: Monitoring (Built In Test) FAIL: Failure management: Associated to failure detected, specific actions are performed. DOWNLOAD: Download mode management E2PROM: EEPROM data storage UNIT CTRL: Drive control and PWM calculation: o Voltage Control o Current Control MTR CTRL: Motor drive control and PWM calculation: o MTR Start up control o MTR Speed Control o MTR Current Control ACTUATION: CAN Actuation A EUI constitutes the digital core of the motor control unit and will implement the following main functionalities: Motor drive control & monitoring Analog to Digital Conversions Failures and data transmission to outside world by CAN Bus Failure storage in EEPROM Maintenance via CAN Bus Software loading via CAN Bus Interfaces with LEDs through IO lines An external EEPROM will be used to store the faults. The EUI will interface with the EEPROM by the mean of a SPI bus. Operational Requirements: 1. The Embedded Unit Instrument (EUI) software operates in five operational modes: INIT OPERATIONAL

3 MAINTENANCE DOWNLOAD FAIL Power On/Reset, VnMode=INIT INIT Mode=OPERATIONAL OPERATIONAL Mode=OPERATIONAL Mode=MAINTENANCE Mode=FAIL FAIL MAINTENANCE Mode=DOWNLOAD DOWNLOAD Figure 1.Modes of operation. Modes of Operation 2. The EUI shall setmode to Fail mode in the following cases (OR logic): When Mode is in Maintenance mode, if Received Message is equal to 12CRLF. When Mode is in Maintenance mode, if Received Message is equal to 12CRLF. When Mode is in Init mode, if Status is in _Error state. 3. When Mode is in Initmode, ifstatus is in No_Errorstate, the EUI shall setmode to Operational mode.

4 4. When Mode is in Operationalmode, ifmaintenance Mode Command state becomes equal to Enable, the EUI shall set Mode to Maintenance mode. 5. When Mode is inmaintenance mode, if MaintenanceState is in Maintenance state and Received Message is equal to CRLF, the EUI shall set Mode to Operational mode and confirm maintenance mode exit by setting TransmitMessage to CRLF. 6. When Mode is inmaintenance mode, if MaintenanceState is in Maintenance state and Received Message is equal to 12CRLF, the EUI shall set Mode to Download mode, wait for 1 second to enter into perform Download management. Timing Requirements 7. The EUI workload for the worst-case shall not exceed 65%. 8. The EUI shall set LED1 to Enableduring execution of the following mode/s: a. Operational 9. The EUI shall set LED2 to Enableduring execution of the following mode/s: a. Maintenance b. Download 10. The EUI shall set off the Voltage control function at 500 Hz frequency. 11. The EUI shall set off the Current control function at 10 Khz frequency. 12. The EUI shall set off the MTR Startup current control function at 20 Khz frequency. 13. The EUI shall set off the MTR Speed current control function at 500 Hz frequency. 14. The EUI shall set off the MTR current control function at 10 Khz frequency. Performance Requirements 15. For the EUI, following shall be available at least as spare: a. 50% of the installed code-memory (FLASH) b. 50% of the installed data memory (RAM) c. 50% of stack memory d. 50% of EEPROM Communication requirements Partition requirements 18. None Software States requirements 19. EUI states

5 20. MTR states 21. Maintenance states Functional Requirements a. Initialization b. BIT (Built In Test) c. Reset Function Fault Management Download Management 24. Interface Management 25. Tolerances and constants 26. ASSIGNMENT DESCRIPTION Analyze Embedded Unit Instrument and write Modes of Operation, Timing Requirements Performance Requirements, Communication requirements, Partition requirements Software States requirements, Software States requirements, Functional Requirements, Fault Management, Download Management, Tolerances and constants The duration of the assignment is 9 Hours.

6 Document contains fallowing points Modes of operation Timing requirement Performance requirements Communication requirements Partition requirements Software state requirement Functional requirement Fault management Download management Interface management Tolerance and constants 5 Marks are awarded for the analyzation 5 Marks are awarded for document

7 Assignment - 3 For the Modes of Operation requirements, write test cases for the above assignment ASSIGNMENT DESCRIPTION: Analyze the embedded unit instrument and write test cases The duration of the assignment is 9 Hours. Document contains the modes of operations and test cases 10 Marks are awarded for the Test case formatted document

8 Assignment - 4 Write test cases with the specified test format using an excel sheet ASSIGNMENT DESCRIPTION: Test Case Scenario () Example Test Step # Test Step Name 1 Pre-Conditions Test Step Description Set all the inputs as mentioned in the Pre- Conditions section 2 Power on the EUI unit Power on the EUI 3 Set Status Set St atus to Error The duration of the assignment is 8 Hours. Document contains test cases with test case format 5 Marks are awarded for the test cases 5 Marks are awarded for the specified test format

9 Assignment - 5 Identify and establish traceability matrix for the developed Test scenarios from the set of EUI requirements. ASSIGNMENT DESCRIPTION: Identify and establish traceability matrix for the developed Test scenarios from the set of EUI requirements. Identify upward traceability (TCs to Req.) Identify downward traceability (Req. to TCs) The duration of the assignment is 9 Hours. Identify upward traceability (TCs to Req.) Identify downward traceability (Req. to TCs) 5 Marks are awarded for the analysis of the system behavior 5 Marks are awarded for the documented result

10 Assignment - 6 Test Case & Defect Management with Testlink / Bugzilla: ASSIGNMENT DESCRIPTION: Using the below link, establish the Testlink requirements, test cases, execution and results and the traceability Generate the Teslink report Go through the Bugzilla possibly with an example. 1. Initial step would be to create a new Test Project and assign QA testers or engineers with tasks. 2. Import Software Requirements and for part of these requirements generates empty Test Cases. Reorganize them into Test Suites. 3.Create a content for empty test cases using test specifications that are being organized into Test suites. 4.Create Regression testing and assigns to applicable test cases. 5.Create a Test Plan, Build and link all Test Cases in Test Suite to this Test Plan. Assign resources to this test plan. 6.Assume QA got there first Build or Release Candidate from development team, execute and record the testing with the result. 7.Assume QA get new Build or Release Candidate with fixes for blocking issues, verify these fixes for blocking issues, execute regression tests. 8.Manager (Test or Engineering) and other project related stakeholders want to see results and status of testing. Then in such a case, these stakeholders including managers can create accounts or use default Guest account to view test results for a particular Build. An overall report gets generated for automated test suites, as a Guest manager is able to view test results at a higher level in graphical format. 9.Suppose new changes happens to existing functionality, its very easy to modify existing test plan and add new test cases or enhance/modify existing test cases and attach them to a particular test plan. 10.Test suites continue to execute as usual by generating various reports. 11. For new project again QA creates a new Test, follows above steps to implement TestLink for there project.

11 The duration of the assignment is 4 Hours. Teslink report,test cases, execution and results 5 Marks are awarded for the finding boundary values 5 Marks are awarded for the explanation

12 Assignment - 7 Using Static analysis method, analyze the attached map file and produce the results as per below requirements. ASSIGNMENT DESCRIPTION: Using Static analysis method, analyze the attached map file and produce the results as per below requirements. RAM memory shall have a reserve of at least 50%. Stack memory shall have a reserve of at least 50%..map file and.lcf files to be used for static analysis on the target is MPC5554 The duration of the assignment is 4 Hours..map file.lcf file for static analysis 10 Marks are awarded for the explain partition problems

13 Assignment - 8 Using the Understand for C/C++ static analysis tool, generate the call tree (control flow) and produce the McCabe complexity and report that the complexity is < 10. ASSIGNMENT DESCRIPTION: Please use the example embedded C code (I2C slave) to generate the call tree (control flow) and produce the McCabe complexity and report that the complexity is < 10. The duration of the assignment is 8 Hours. Generate the call tree (control flow) Produce the McCabe complexity and report 5 Marks are awarded for the event table, transition tree 5 Marks are awarded for the test script legal test cases, test script illegal, test cases test script guards

14 Assignment - 9 Create a test plan for an embedded project ASSIGNMENT DESCRIPTION: Create a test plan for an embedded project consisting of the below: Automotive ECU project consisting of 50 SRS approx. Codewarrior IDE with Freescale s HCS12 as target processor 100% code coverage MISRA C 2004 guidelines can be used Example Template SOFTWARE VERIFICATION PLAN FOR <XXX> Introduction Purpose Responsibilities Change control Compliance Abbreviations and acronyms <XXX>_SVP Variant: <yyy> Baseline Applicable and reference documents External applicable documents Internal applicable documents Verification Responsibility Organization Independence Verification Methods Testing Method Review Method Analysis method Verification activities Planning process verification Verification of system requirements Verification of high-level-requirements Verification of outputs of integration Verification of Testing results

15 Verification Environment Testing Environment Testing tools Tools qualification Traceability to compliance mapping Additional considerations Partitioning, compiler, COTS Standards, Checklists and guidelines The duration of the assignment is 8 Hours. Test plan for an embedded project 10 Marks are awarded for the test cases

16 Assignment - 10 Using a version control tool such as SVN, create a CI (configuration item) baseline for the EST class materials with the help of SCM process ASSIGNMENT DESCRIPTION: Using a version control tool such as SVN, create a CI (configuration item) baseline for the EST class materials with the help of the below SCM process : SCI (software configuration identification) Software configuration control Software configuration status accounting Software configuration audit The duration of the assignment is 4 Hours. CI (configuration item) baseline for the EST 5 Marks are awarded for the test revalidation, test selection 5 Marks are awarded for the test minimization, test prioritization

Fredrick M. Cady. Assembly and С Programming forthefreescalehcs12 Microcontroller. шт.

Fredrick M. Cady. Assembly and С Programming forthefreescalehcs12 Microcontroller. шт. SECOND шт. Assembly and С Programming forthefreescalehcs12 Microcontroller Fredrick M. Cady Department of Electrical and Computer Engineering Montana State University New York Oxford Oxford University