Project 1 - V&V SW Analysis - I
TEST PLAN
"Features of New Mobile Phone"
INTRODUCTION –
The Test Plan is designed to prescribe the scope, approach, resources, and user acceptance of all testing activities of the project (features of new mobile phone).
The plan identifies the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and the risks/assumptions associated with the plan
1.TEST STRATEGY-
1.1 TEST TYPE –
In the Test plan, to test the features of new mobile phone we use BLACKBOX TESTING which is one of the techniques of UNIT TESTING. It involves with the user interfaces of the inputs and outputs of the software applications. It usually doesn’t care about what the internal structure of the code, as it deals with only inputs and outputs.
USER SPECIFICATION MODULE NAME DESCRIPTION
US-1 COMPANY LOGO PRODUCT OWNER - When long pressed the power button of the phone shall switch on with a company logo at the centre of the screen.
US-2 APP ICONS (GRID MODE) CUSTOMER – When the power button is pressed my phone is switched ON and all my icons of the APPS shall be present in the grid.
US-3 CALL THE PHONE ICON PRODUCT OWNER – When the phone is powered ON, I shall see the “call the phone” icon as the first icon at the bottom bar of my screen.
US-4 DICTIONARY ICON PRODUCT OWNER – When the phone is powered ON, I shall see the “Dictionary” icon as the second icon at the bottom bar of my screen.
US-5 CALL THE PHONE
(CONTACTS) PRODUCT OWNER – When I clicked my “call the phone” icon, all the contacts shall be visible based on chronological order.
US-6 DICTIONARY ICON
(SEARCH BAR) PRODUCT OWNER – When I clicked my “Dictionary” icon, a search bar shall appear at the middle of the screen to let me search the meanings of the words I desire.
US-7 GOOD-BYE MESSAGE PRODUCT OWNER – When I long pressed my “power on” button, my phone shall be switched off saying “Good-Bye” message.
US-8 FONT PRODUCT OWNER – My font in the mobile shall always be “Calibri (Body)” and shall be of size 12.
US-9 USER INTERFACE(UI) CUSTOMER – I need my UI to be touch responsive.
US-10 HARD BUTTONS CUSTOMER – My mobile phone should have no hard buttons.
1.2 SCOPE OF TESTING -
1.2.1 FEATURE TO BE TESTED –
All the features of new mobile phone which were defined in software requirement specifications are need to tested.
1.2.2 FEATURE NOT TO BE TESTED -
These features are not be tested because they are not included in the software requirement specifications
- User Interfaces
- Hardware Interfaces
- Software Interfaces
- Database logical
- Communications Interfaces
- Website Security and Performance
1.3 RISK/ASSUMPTIONS –
RISK MITIGATION
Team member lack the required skills for website testing. Plan training course to skill up your members
A lack of cooperation negatively affects your employees' productivity Encourage each team member in his task, and inspire them to greater efforts.
Wrong budget estimate and cost overruns Establish the scope before beginning work, pay a lot of attention to project planning and constantly track and measure the progress
1.4 Test Logistics -
1.4.1 Who will test?
The project should use outsource members as the tester to save the project cost.
1.4.2 When will test occur?
The tester will start the test execution when all the following inputs are ready
- Software is available for testing
- Test Specification is created
- Test Environment is built
- Enough human resource for testing
2. TEST OBJECTIVE -
The test objectives are to verify the Functionality of New Mobile Phone features, the project should focus on testing the mobile phone operations such as user interface, Touch Management, App icons, and grid view of app icons...etc. to guarantee all these operations can work normally in real world environment.
3. RESOURCE PLANNING –
3.1 SYSTEM RESOURCE -
S. NO RESOURCES DESCRIPTION
1. Server Need a source file server which install LDRA TBurn.
2. Test Tool Develop a Test tool which can auto generate the test result to the pre-defined form and automated test execution.
3. Network Setup a LAN Gigabit and 1 internet line with the speed at least 5 Mb/s
4. Computer At least 4 computer run Windows 10, Ram 4GB, CPU 3.4GHZ
3.2 HUMAN RESOURCE -
S.N0 MEMBER TASKS
1. Test Manager Manage the whole project, Define project directions
Acquire appropriate resources
2. Test Identifying and describing appropriate test
techniques/tools/automation architecture
Verify and assess the Test Approach
Execute the tests, Log results, Report the defects.
Outsourced members
3. Developer in Test Implement the test cases, test program, test suite etc.
4. Test Administrator Builds up and ensures test environment and assets are managed and maintained Support Tester to use the test environment for test execution
5. QA Members Take in charge of quality assurance
Check to confirm whether the testing process is meeting specified requirements
4. USER ACCEPTANCE TESTING -
PURPOSE: this test focuses on validating the business logic. It allows the end users to complete one final review of the system prior to deployment.
TESTERS: the UAT is performed by the end users (L1, L2 and L3).
METHOD: Since the business users are the most indicated to provide input around business needs and how the system adapts to them, it may happen that the users do some validation not contained in the scripts. Test team write the UAT test cases based on the inputs from End user (L1, L2 and L3 users) and Business Analyst’s.
TIMING: After all other levels of testing (Exploratory and Functional) are done. Only after this test is completed the product can be released to production.
The product is still under development stage and is yet to be UA (User Acceptance) tested.
5. TEST DELIVERABLES -
Test deliverables are provided as below
5.1 BEFORE TESTING PHASE -
- Test plans document.
- Test cases documents
- Test Design specifications.
5.2 DURING THE TESTING -
- Test Tool
- Simulators.
- Test Data
- Test Trace-ability Matrix
- Error logs and execution logs.
5.3 AFTER THE TESTING CYCLES IS OVER -
- Test Results/reports
- Defect Report
- Installation/ Test procedures guidelines
- Release notes.