Project 1 - V&V SW Analysis - I

LIVE BATCH(Preeti)

TEST PLAN:

• Test Plan is a document that consists of all future testing-related activities.
• It is prepared at the project level and in general, it defines work products to be tested, how they will be tested, and test type distribution among the testers.
• Before starting testing there will be a test manager who will be preparing a test plan. In any company whenever a new project is taken up before the tester involves in the testing the test manager of the team would prepare a test Plan.
• It acts as a quick guide for the testing process
• It helps to avoid out-of-scope functionalities
• It determines the time, cost, and effort.
• It Provides a schedule for testing activities.
• Test Plan Document can be used for similar projects.
• It helps to understand the test details.
• It helps in determining the quality of software applications.

Test Plan Attributes:-

There are many attributes in Test Plan as follow,

• Objective: It describes the aim of the test plan, whatever the good process and procedure they are going to follow in order to give quality software to customers. The overall objective of the test is to find as many defects as possible and to make software bug free. The test objective must be broken into components and sub-components.

• Test Strategy: It is a crucial document that is to be performed and usually designed by the Test Manager. It helps to determine Test Effort and Test cost. Test strategy helps to determine the features that are going to be tested and the features that will not be tested. The scope can be divided into two parts:

  • In-Scope: The modules that are to be tested rigorously.
  • Out-Scope: The modules that are not to be tested rigorously.

• Testing Methodology: The methods that are going to be used for testing depend on application to application. The testing methodology is decided based on the feature and application requirements. Since the testing terms are not standard, one should define what kind of testing will be used in the testing methodology. So that everyone can understand it.

• Approach: The approach of testing different software is different. It deals with the flow of applications for future references.

• Assumptions: In this phase, certain assumptions will be made.

  Example:

  • The testing team will get proper support from the development team.
  • The tester will get proper knowledge transfer from the development team.
  • Proper resource allocation will be given by the company to the testing department.

• Risk: All the risks that can happen if the assumption is breaking. For Example, in the case of wrong budget estimation, the cost may overrun. Some reason that may lead to risk is:

  • Test Manager has poor management skills.
  • Hard to complete the project on time.
  • Lack of cooperation.

• Backup/Mitigation Plan- If any risk is involved then the company must have a backup plan, the purpose is to avoid errors. Some points to resolve/avoid risk:

  • Test priority is to be set for each test activity.
  • Managers should have leadership skills.
  • Training course for the testers.

• Roles and Responsibilities: All the responsibilities and role of every member in a particular testing team has to be recorded.

  Example:

  • Test Manager: Manages the project, takes an appropriate resource, and gives project direction.
  • Tester: Identify the testing technique, verify the test approach, and save project cost.
• Scheduling: Under this, it will record the start and the end date of each and every testing-related activity. For Example, writing test case date and ending test case date.
• Defect Tracking: It is an important process in software engineering as lots of issue arises when you develop a critical system for business. If there is any defect found while testing and that defect must be given to the developer team.

• Test Environment- It is the environment which the testing team will use i.e. the list of hardware and software, while testing the application, the things which are said to be tested will be written under this section. The installation of software is also checked under this.

  Example:

  • Software configuration on different operating systems, such as Windows, Linux, Mac, etc.
  • Hardware Configuration depends on RAM, ROM, etc.

• Entry and Exit Criteria: The set of conditions that should be met in order to start any new type of testing or to end any kind of testing.

  Entry Condition:

  • Necessary resources must be ready.
  • The application must be prepared.
  • Test data should be ready.

  Exit Condition:

  • There should not be any major bug.
  • Most test cases should be passed.
  • When all test cases are executed.

• Test Automation: It consists of the features that are to be automated and which features are not to be automated.

  • If the feature has lots of bugs then it is categorized as Manual Testing.
  • If the feature is frequently tested then it can be automated.

• Deliverables- It is the outcome from the testing team and that is to be given to the customers at the end of the project.

  Before the testing phase:

  • Test plan document.
  • Test case document.
  • Test design specification.

  During the testing phase:

  • Test scripts.
  • Test data.
  • Error logs.

  After the testing phase:

  • Test Reports.
  • Defect Report.
  • Installation Report

• This is the flow chart for the if else if ladder . if the IF condition is true then that statement inside IF condition is printed in output console.
• If the IF condition fails then it comes to the successsing IF-ELSE condition and checks if it is true.If it is true then that statemnet is displayed in console of output.
• And if 1st IF-Else condition is false then it comes to the next IF-Else condition and it goes on until all the conditions given in the requirements are covered and then if all the conditions fails then finally the else condition's statemnt is printed in the output console.

TEST Plan for new mobile phone:

if(owner long pressed the power button of phone){

print("company logo should appear at the centre of screen");

}

else if(owner pressed the power button is pressed once){

print("phone should be switched ON and all the icons of the APPS should be present in the grid");

}

else if( owner powers ON the phone){

print("call the phone icon should be the first icon presnt at the bottom bar of the screen");

}

else if( owner powers ON the phone){

print(" Dictionary icon should be the second icon presnt at the bottom bar of the screen");

}

else if(owner clicks on the call the phone icon){

print("all the contacts in the phone should be displayed based on chronological order");

}

else if(owner clicks on the Dictionary icon){

print("Search bar should appear at the middle of the screen to search the meanings of the words typed");

}

else if(owner long pressed the power button){

print("phone should be switched OFF and saying Good-Bye");

}

else if(Font and size of Owner's phone){

print("mobile should always be calibri (Body) and size is to be 12");

}

else if(Touch response of owner's phone){

print("UI of owner's phone should be touch responsive");

}

else if(buttons of owner's phone){

print("owner's phone should not have hard buttons");

}

else {

print("There is some malfunction in this product");

}