SayPro Conduct test planning and estimation.

South African rand (R) – ZAR
  • United States dollar ($) – USD
  • South African rand (R) – ZAR

ASSESSMENT CRITERION RANGELevels may include but are not limited to: Component testing, Integration testing, Acceptance testing and System testingCreate a Test PlanWhat is a Test Plan?A test plan is a detailed document that outlines the test strategy, Testing objectives, resources (manpower, software, hardware) required for testing, test schedule, Test Estimation and test deliverables.The test plan […]

Tags: ,

Description

ASSESSMENT CRITERION RANGELevels may include but are not limited to: Component testing, Integration testing, Acceptance testing and System testingCreate a Test PlanWhat is a Test Plan?A test plan is a detailed document that outlines the test strategy, Testing objectives, resources (manpower, software, hardware) required for testing, test schedule, Test Estimation and test deliverables.The test plan serves as a blueprint to conduct software testing activities as a defined process which is minutely monitored and controlled by the test manager.Let’s start with following scenarioIn a meeting, you want to discuss the Test Plan with the team members, but they are not interested – .In such case, what will you do? Select your answer as following figurehttps://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_2.jpgIImportance of Test PlanMaking Test Plan has multiple benefits

  • Test Plan helps us determine the effort needed to validate the quality of the application under test
  • Help people outside the test team such as developers, business managers, customers understand the details of testing.
  • Test Plan guides our thinking. It is like a rule book, which needs to be followed.
  • Important aspects like test estimation, test scope, Test Strategy are documented in Test Plan, so it can be reviewed by Management Team and re-used for other projects.

How to write a Test PlanYou already know that making a Test Plan is the most important task of Test Management Process. Follow the seven steps below to create a test plan as per IEEE 829

  • Analyze the product
  • Design the Test Strategy
  • Define the Test Objectives
  • Define Test Criteria
  • Resource Planning
  • Plan Test Environment
  • Schedule & Estimation
  • Determine Test Deliverables

https://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_3.pngStep 1) Analyze the productHow can you test a product without any information about it? The answer is Impossible. You must learn a product thoroughly before testing it.The product under test is Guru99 banking website. You should research clients and the end users to know their needs and expectations from the application

  • Who will use the website?
  • What is it used for?
  • How will it work?
  • What are software/ hardware the product uses?
  • You can use the following approach to analyze the site

https://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_4.jpgYou should take a look around this website and also review product documentation. Review of product documentation helps you to understand all the features of the website as well as how to use it. If you are unclear on any items, you might interview customer, developer, designer to get more information.Step 2) Develop Test StrategyTest Strategy is a critical step in making a Test Plan. A Test Strategy document, is a high-level document, which is usually developed by Test Manager. This document defines:

  • The project’s testing objectives and the means to achieve them
  • Determines testing effort and costs

Back to your project, you need to develop Test Strategy for testing that banking website. You should follow steps belowhttps://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_6.pngStep 2.1) Define Scope of Testing

  • Before the start of any test activity, scope of the testing should be known. You must think hard about it.
  • The components of the system to be tested (hardware, software, middleware, etc.) are defined as "in scope"
  • The components of the system that will not be tested also need to be clearly defined as being "out of scope."
  • Defining the scope of your testing project is very important for all stakeholders. A precise scope helps you
  • Give everyone a confidence & accurate information of the testing you are doing
  • All project members will have a clear understanding about what is tested and what is not
  • How do you determine scope your project?

To determine scope, you must –

  • Precise customer requirement
  • Project Budget
  • Product Specification
  • Skills & talent of your test team
  • Now should clearly define the "in scope" and "out of scope" of the testing.

Nonfunctional testing such as stress, performance or logical database currently will not be tested. (out of scope)Problem ScenarioThe customer wants you to test his API. But the project budget does not permit to do so. In such a case what will you do?Well, in such case you need to convince the customer that Api Testing is extra work and will consume significant resources. Give him data supporting your facts. Tell him if Api Testing is included in-scope the budget will increase by XYZ amount.The customer agrees and accordingly the new scopes, out of scope items areIn-scope items: Functional Testing, Api TestingOut of scope items: Database Testing, hardware & any other external interfacesStep 2.2) Identify Testing Type

  • A Testing Type is a standard test procedure that gives an expected test outcome.
  • Each testing type is formulated to identify a specific type of product bugs. But, all Testing Types are aimed at achieving one common goal “Early detection of all the defects before releasing the product to the customer”
  • The commonly used testing types are described as following figure

https://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_7.pngThere are tons of Testing Types for testing software product. Your team cannot have enough efforts to handle all kind of testing. As Test Manager, you must set priority of the Testing Types

  • Which Testing Types should be focused for web application testing?
  • Which Testing Types should be ignored for saving cost?
  • Now let’s practice with your project. The product you want to test is a banking website.
  • Which Testing Types should you focus in this case?

Step 2.3) Document Risk & IssuesRisk is future’s uncertain event with a probability of occurrence and a potential for loss. When the risk actually happens, it becomes the ‘issue’.In the article Risk Analysis and Solution, you have already learned about the ‘Risk’ analysis in detail and identified potential risks in the project.In the Test Plan, you will document those risks

Risk Mitigation
Team member lack the required skills for website testing. Plan training course to skill up your members
The project schedule is too tight; it’s hard to complete this project on time Set Test Priority for each of the test activity.
Test Manager has poor management skill Plan leadership training for manager
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

Step 2.4) Create Test LogisticsIn Test Logistics, the Test Manager should answer the following questions:

  • Who will test?
  • When will the test occur?
  • Who will test?

You may not know exact names of the tester who will test, but the type of tester can be defined.To select the right member for specified task, you have to consider if his skill is qualified for the task or not, also estimate the project budget. Selecting wrong member for the task may cause the project to fail or delay.Person having the following skills is most ideal for performing software testing:

  • Ability to understand customers point of view
  • Strong desire for quality
  • Attention to detail
  • Good cooperation

In your project, the member who will take in charge for the test execution is the tester. Base on the project budget, you can choose in-source or outsource member as the tester.When will the test occur?Test activities must be matched with associated development activities.You will start to test when you have all required items shown in following figurehttps://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_8.pngStep 3) Define Test ObjectiveTest Objective is the overall goal and achievement of the test execution. The objective of the testing is finding as many software defects as possible; ensure that the software under test is bug free before release.

  • To define the test objectives, you should do 2 following steps
  • List all the software features (functionality, performance, GUI…) which may need to test.
  • Define the target or the goal of the test based on above features

In the previous topic, you have already analyzed the requirement specs and walk through the website, so you can create a Mind-Map to find the website features as followinghttps://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_9.pngThis figure shows all the features which the website may have.Based on above features, you can define the Test Objective of the project as followingCheck that whether website functionality (Account, Deposit…) is working as expected without any error or bugs in real business environmentCheck that the external interface of the website such as UI is working as expected and & meet the customer needVerify the usability of the website. Are those functionalities convenient for user or not?Step 4) Define Test CriteriaTest Criteria is a standard or rule on which a test procedure or test judgment can be based. There’re 2 types of test criteria as followingSuspension CriteriaSpecify the critical suspension criteria for a test. If the suspension criteria are met during testing, the active test cycle will be suspended until the criteria are resolved.Example: If your team members report that there are 40% of test cases failed, you should suspend testing until the development team fixes all the failed cases.https://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_10.pngExit CriteriaIt specifies the criteria that denote a successful completion of a test phase. The exit criteria are the targeted results of the test and are necessary before proceeding to the next phase of development. Example: 95% of all critical test cases must pass.Some methods of defining exit criteria are by specifying a targeted run rate and pass rate.Run rate is ratio between number test cases executed/total test cases of test specification. For example, the test specification has total 120 TCs, but the tester only executed 100 TCs, So the run rate is 100/120 = 0.83 (83%)Pass rate is ratio between numbers test cases passed / test cases executed. For example, in above 100 TCs executed, there’re 80 TCs that passed, so the pass rate is 80/100 = 0.8 (80%)

  • This data can be retrieved in Test Metric documents.
  • Run rate is mandatory to be 100% unless a clear reason is given.
  • Pass rate is dependent on project scope, but achieving high pass rate is a goal.

Step 5) Resource PlanningResource plan is a detailed summary of all types of resources required to complete project task. Resource could be human, equipment and materials needed to complete a projectThe resource planning is important factor of the test planning because helps in determining the number of resources (employee, equipment…) to be used for the project. Therefore, the Test Manager can make the correct schedule & estimation for the project.This section represents the recommended resources for your project.Human ResourceThe following table represents various members in your project team

No. Member Tasks
1. Test Manager Manage the whole projectDefine project directionsAcquire appropriate resources
2. Tester Identifying and describing appropriate test techniques/tools/automation architectureVerify and assess the Test ApproachExecute the tests, Log results, Report the defects.Tester could be in-sourced or out-sourced members, base on the project budgetFor the task which required low skill, I recommend you choose outsourced members to save project cost.
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 maintainedSupport Tester to use the test environment for test execution
5. SQA members Take in charge of quality assuranceCheck to confirm whether the testing process is meeting specified requirements

System ResourceFor testing, a web application, you should plan the resources as following tables:

No. Resources Descriptions
1. Server Install the web application under testThis includes a separate web server, database server, and application server if applicable
2. Test tool The testing tool is to automate the testing, simulate the user operation, generate the test resultsThere are tons of test tools you can use for this project such as Selenium, QTP…etc.
3. Network You need a Network include LAN and Internet to simulate the real business and user environment
4. Computer The PC which users often use to connect the web server

Step 6) Plan Test EnvironmentWhat is the Test EnvironmentA testing environment is a setup of software and hardware on which the testing team is going to execute test cases. The test environment consists of real business and user environment, as well as physical environments, such as server, front end running environment.How to setup the Test EnvironmentBack to your project, how do you set up test environment for this banking website?To finish this task, you need a strong cooperation between Test Team and Development Teamhttps://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_12.pngYou should ask the developer some questions to understand the web application under test clearly. Here’re some recommended questions. Of course, you can ask the other questions if you need.

  • What is the maximum user connection which this website can handle at the same time?
  • What are hardware/software requirements to install this website?
  • Does the user’s computer need any particular setting to browse the website?

Following figure describes the test environment of the banking websitehttps://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_13.jpgStep 7) Schedule & EstimationIn the article Test estimation, you already used some techniques to estimate the effort to complete the project. Now you should include that estimation as well as the schedule to the Test PlanningIn the Test Estimation phase, suppose you break out the whole project into small tasks and add the estimation for each task as below

Task Members Estimate effort
Create the test specification Test Designer 170 man-hour
Perform Test Execution Tester, Test Administrator 80 man-hour
Test Report Tester 10 man-hour
Test Delivery 20 man-hour
Total 280 man-hour

Then you create the schedule to complete these tasks.Making schedule is a common term in project management. By creating a solid schedule in the Test Planning, the Test Manager can use it as tool for monitoring the project progress, control the cost overruns.To create the project schedule, the Test Manager needs several types of input as below:

  • Employee and project deadline: The working days, the project deadline, resource availability are the factors which affected to the schedule
  • Project estimation: Base on the estimation, the Test Manager knows how long it takes to complete the project. So he can make the appropriate project schedule
  • Project Risk : Understanding the risk helps Test Manager add enough extra time to the project schedule to deal with the risks

Step 8) Test DeliverablesTest Deliverables is a list of all the documents, tools and other components that has to be developed and maintained in support of the testing effort.There are different test deliverables at every phase of the software development lifecycle.https://cdn.guru99.com/images/TestManagement/testmanagement_article_2_4_15.pngPlease visit our website at www.saypro.online Email: info@saypro.online Email: info@saypro.online Call: + 27 11 071 1903 WhatsApp: + 27 84 313 7407. Comment below for any questions and feedback. For SayPro Courses, SayPro Jobs, SayPro Community Development, SayPro Products, SayPro Services, SayPro Consulting, and SayPro Advisory visit our website to www.saypro.online

Reviews

There are no reviews yet.

Be the first to review “SayPro Conduct test planning and estimation.”

Your email address will not be published. Required fields are marked *