Purpose of test case template is to provide sufficient amouint of information about test cases for test case users. Intention is to keep test case template as simple as possible. Test case template does not contains any information about test execution schedule, intervals how often it will be executed or so. This is defined in test execution management tool(s) what ever they might be. Same template should be used despite is test case concerning UX or Core.
Template contains following contains following fields:
TC Title: (mandatory) <Descriptive title for test case>
TC ID: (mandatory) <Test case unique identifier>
Requirement: (Optional) <Requirement reference>
Type: (Mandatory) <Type of test case>
Domain: <Vertical> Values: Common, Handheld, Netbook, In-Vehicle, Connected TV, Media Phone
Feature: (Mandatory) <Bugzilla Feature>
Subfeature: (optional) Can be used when test case designer wants to identify more detailed level what is tested.
Component: <Bugzilla Component>
Execution Type: <Manual, Auto>
Test Case State: <Design/Ready/Approved>
Description:
Purpose: <Test case purpose here. What is tried to achieve with this specific TC> Method: <Short description of TC method here, e.g., how measurement is done and what the result describes. Could be a link to another document. This field is optional> References: <Link to web, wiki or similar place where more detailed information is available (if any) for this TC> Pre-conditions: <Specific description of things or settings needed prior to this TC run. E.g. memory card in device and audio clip at path /home/user/audioclips> Run instructions: <Run instructions specific for this TC. Describe instructions by steps (n) – refer to PASS / FAIL criteria for this step.> Pass/Fail criteria: <What are the criterion that TC shall fulfil in order to consider TC as passed. For instance, test case returns pass and audio is audible from Wired Headset. Describe PASS / FAIL criteria for each run step.> Post-conditions: <Description what needs to be done after running the test case to return to standard state.> Test Environment: <Link to a document describing manual or automatic test environment. No test cases having dependencies to corporate network or other proprietary SW / HW> Required test data: <Description of specific test data / parameters for this TC with unambiguous file references> Change history: <Description of modifications done to this TC, with name of author. Change history of last 5 changes at least>
TC Title: DATAFLOW-FS-Copy-File-eMMC-to-MMC TC ID: DATAFLOW-FS-Copy-File-eMMC-to-MMC Requirement Type: Functional Domain: Handheld Feature: Subfeature: copy Component: Execution Type: Test Case State: Approved Description:
Purpose: This case tests file can be copied from eMMC to eMMC Method: Test case copies file from eMMC to eMMC, file block size 1kB, block count 1000 References: None Pre-conditions: Test asset and MIN test frame Work is installed to the device. Memory card must be mounted in device. Test must be executed as root. Run instructions: Pass/Fail criteria: Test case returns passed if operation was succesfull. Result is logged into /var/log/tests/." Post-conditions: None Test Environment: Handheld device Required test data: None Change history: