Project 1 - V&V SW Analysis - I

Test Plans:

Test plans are an integral part of the software verification and validation process. It outlines the objectives, scope, and resources required for testing, as well as the schedule and test environment.

The steps involved in creating the test plans may vary depending on the specific project and organization. The general outline of the steps typically followed when creating a test plans are:

1.Determine the purpose and goals of testing activities.
2.Determine the boundaries and extent of testing.
3.Define the specific test deliverables like test cases, test scripts.
4.Determine the Testing Strategy such as integration testing,unit testing
5.Determine the required test environment, including hardware, software, and network configuration.
6.Determine the necessary resources for testing, such as human resources, testing equipments.
7.Develop a timeline and schedule for the testing activities.
8.Identify test risks and Mitigation strategies.
9.Determine the specific testing techniques and methodologies that will be used.
10.Define Test Entry and Exit Criteria.
11.Create test cases and test data.
12.Establish defect management process.
13.Develop test execution and evaluation plan.
14.Create test reporting mechanisms.
15.Review and approve the test plan.

Test plans can be of several types, some of the common types of test plans are:
1.Master Test Plan 2.System Test Plan 3.Acceptance Test Plan 4.Integration Test Plan
5.Performance Test Plan 6.Security Test Plan 7.Regression Test Plan 8.User Interface Test Plan

White box testing and black box testing are two different approaches to software testing, each with its own focus and objectives. Here's an overview of white box testing and black box testing:

White Box Testing:
White box testing, also known as clear box testing or structural testing, is a testing technique that examines the internal structure and implementation of the software being tested. In white box testing, the tester has access to the internal code, data structures, and logic of the software system.

The primary goal of white box testing is to validate the correctness of the internal code and ensure that all paths, conditions, and branches within the code are tested.

White box testing is focused on testing specific code segments, functions, or components. It aims to achieve high code coverage and exercises various code paths, branches, and conditions.
It include statement coverage, branch coverage, path coverage, and other code-focused criteria. It is effective in validating the logic, flow, and integration of code components.

Black Box Testing:
Black box testing is a testing technique that focuses on the external behavior of the software without considering its internal structure, design, or implementation details. Testers performing black box testing have no knowledge of the internal workings of the software.

The primary goal of black box testing is to validate the software against the specified requirements and ensure that it functions as expected from a user's perspective.

Black box testing is based on the software requirements, specifications, or functional documentation. Testers are unaware of the internal code or implementation details of the software.
It aims to validate the software's functionality, usability, and adherence to requirements from an end-user perspective.
It include equivalence partitioning, boundary value analysis, use case testing, and scenario-based testing.

Test Plans:

1.If the power button is long pressed then switch on phone with company logo at center of the screen.

2.If the power button is pressed, all the icons of the APPS should be present in grid.

3.If the phone is powered ON , "call the phone" icon should be the first icon at bottom bar of the screen.

4.If the phone is powered ON , "Dictionary" icon should be the second icon at bottom bar of the screen.

5.If "call the phone" icon is clicked all the contacts should be visible based on chronological order.

6.While clicking on "Dictionary" icon, a search bar should appear at the middle of the screen.

7.If the power button is long pressed then phone should switch off with "Good-Bye" message.

8.The fonts in moblie should be "calibri" and of size 12.

9.The UI should be touch responsive.

10.The phone should not have any hard buttons.