Looking for breakthrough ideas for innovation challenges? Try Patsnap Eureka!

Software testing workload estimation method

A technology of software testing and workload, which is applied in the field of software testing workload estimation, can solve problems such as large gaps in estimation results and few estimation models, and achieve the effects of high reliability, low complexity, and evaluation of testing risks

Inactive Publication Date: 2015-10-14
FOSHAN LANGDA INFORMATION TECH
View PDF2 Cites 7 Cited by
  • Summary
  • Abstract
  • Description
  • Claims
  • Application Information

AI Technical Summary

Problems solved by technology

[0003] However, at present, there are few estimation models specifically for the field of software testing, and due to different enterprise conditions and business fields, the current workload budget for a certain testing work is often estimated based on personal work experience, and Estimated results differ greatly from actual results

Method used

the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
View more

Examples

Experimental program
Comparison scheme
Effect test

example 1

[0021] Example 1: Bank Securities System Development

[0022] Software testing effort estimation includes the following steps:

[0023] a) Estimate the most likely number of test cases based on functional requirements and system design specifications. For small projects, use 10 as a unit to estimate the number of test cases, and for large projects, use 100 as a unit to estimate the test case data.

[0024] The number of functional test cases in the example project is: 1100. All trial cases are test cases that can be executed in real time.

[0025] b) Define the time required to execute a test case, and assume that all test cases pass when the test case is executed for the first time. It is necessary to separate the execution time of the test cases that can judge the execution results in real time and the test cases that require batch processing or special processing to judge the test results. The time it takes for testers to execute a real-time test case in the example proj...

example 2

[0041] Example 2: Development of bank account opening system

[0042] Software testing effort estimation includes the following steps:

[0043] a) The number of functional test cases in the example project is: 3100. All trial cases are test cases that can be executed in real time.

[0044] b) The time it takes for testers to execute a real-time test case in the example project: 8 minutes

[0045] c) In the example project, the capability maturity level of the company group is a definable level, so the time spent to execute all functional test cases: 3100 * 8 minutes * 3 (factor) = 74400 minutes

[0046] d) In the example project, the requirements for non-functional testing are not sure, so the time spent after adding non-functional testing is 74400 minutes + 74400 minutes * 25% = 93000 minutes

[0047] e) Add the workload of user requirements testing to the results obtained in d) to obtain the total time for testing implementation. In the example project, regression testin...

example 3

[0052] Example 3: Development of a questionnaire survey system for bank customers

[0053] Software testing effort estimation includes the following steps:

[0054] a) In the example, according to the function point analysis of the requirements specification, the number of functional test cases is: 5720. All trial cases are test cases that can be executed in real time.

[0055] b) The time it takes for testers to execute a real-time test case in the example project: 5 minutes

[0056]c) In the example project, the capability maturity level of the company group is a definable level, so the time spent to execute all functional test cases: 5720 * 5 minutes * 3 (factor) = 85800 minutes

[0057] d) In the example project, it is determined that the non-functional requirements are very low, so the time spent after adding non-functional tests is 85800 minutes + 85800 minutes * 10% = 94380 minutes

[0058] e) Add the workload of user requirements testing to the results obtained in d...

the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
Login to View More

PUM

No PUM Login to View More

Abstract

The invention discloses a software testing workload estimation method which is low in complexity and small in estimation error. The software testing workload in a software development project is estimated by virtue of parameters of number of most-likely test cases according to estimation function test needs, time for implementing one test case, software development maturity capability of a working team, and a condition whether software needs to non-functional test or not. The software testing workload estimation method is beneficial to making a test scheme in software development project management more accurately, arranging test progress, regulating test resources and estimating test risks.

Description

technical field [0001] The invention relates to the technical field of software testing, in particular to a software testing workload estimation method. Background technique [0002] Software testing is an effective method to ensure software quality, and accurate prediction of testing time and workload is the primary task of software testing. An excellent software estimation model is helpful for test managers to more accurately formulate test plans, arrange test progress, adjust test resources, and evaluate test risks. [0003] However, at present, there are few estimation models specifically for the field of software testing, and due to different enterprise conditions and business fields, the current workload budget for a certain testing work is often estimated based on personal work experience, and There is a big difference between the estimated results and the actual results. Contents of the invention [0004] The technical problem mainly solved by the present inventi...

Claims

the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
Login to View More

Application Information

Patent Timeline
no application Login to View More
IPC IPC(8): G06F11/36
Inventor 李鸿雁
Owner FOSHAN LANGDA INFORMATION TECH
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Patsnap Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Patsnap Eureka Blog
Learn More
PatSnap group products

Browse by: Latest US Patents, China's latest patents, Technical Efficacy Thesaurus, Application Domain, Technology Topic, Popular Technical Reports.

© 2024 PatSnap. All rights reserved.Legal|Privacy policy|Modern Slavery Act Transparency Statement|Sitemap|About US| Contact US: help@patsnap.com