Skip to main content

Test Estimation Techniques

Estimating effort for test is one of the major and important tasks in SDLC. Correct estimation
helps in testing the Software with maximum coverage. This section describes some of the
techniques which can be useful during the estimating of effort for testing.

Functional Point Analysis

This method is based on the analysis of functional user requirements of the Software with
following categories:
●Outputs
●Inquiries
●Inputs
●Internal files
●External files

Test Point Analysis
This estimation process is used for function point analysis for Black box or Acceptance
testing. It is use the main elements of this method are: Size, Productivity, Strategy,
Interfacing, Complexity and Uniformity etc.

Mark-II method
 
It is estimation method used for analysis and measuring the estimation based on end user
functional view. The procedure for Mark-II method is:
●Determine the View Point
●Purpose and Type of Count
●Define the Boundary of Count
●Identify the Logical transactions
●Identify and Categorize Data Entity

Types
●Count the Input Data Element Types
●Count the Functional Size

Miscellaneous
You can use other popular estimation techniques like:
●Delphi Technique
●Analogy Based Estimation
●Test Case Enumeration Based Estimation
●Task (Activity) based Estimation and IFP UG method

Comments

Post a Comment

Popular posts from this blog

Mobile Application Testing Checklist

1. DEVICE SPECIFIC CHECKS 1.1  Can the app be installed on the device? 1.2 Does the app behave as designed/desired if there is an incoming call? 1.3 Does the app behave as designed/desired if there is an incoming SMS? 1.4 Does the app behave as designed/desired if the charger is connected? 1.5 Does the app behave as designed/desired if the charger is disconnected? 1.6 Does the app behave as designed/desired if the device goes to sleeping mode 1.7 Does the app behave as designed/desired if the device resumes from sleeping mode 1.8  Does the app behave as designed/desired if the device resumes from lock screen? 1.9    Does the app behave as designed/desired if the device is tilted? 1.10  Does the app behave as designed/desired if the device is shaken? 1.11 Does the app behave as designed/desired if a local message is coming from another app (think   of: calendar reminders, to-do task etc.). 1.12 Does the app behave as designed/desired if a push message i...
Post a Comment
Read more

Test Scenarios for Excel Export Functionality

1. The file should get exported in the proper file extension. 2. The file name for the exported Excel file should be as per the standards e.g. if the file name is using the timestamp, it should get replaced properly with an actual timestamp at the time of exporting the file. 3. Check for date format if exported Excel file contains the date columns. 4. Check number formatting for numeric or currency values. Formatting should be the same as shown on the page. 5. The exported file should have columns with proper column names. 6. Default page sorting should be carried in the exported file as well. 7. Excel file data should be formatted properly with header and footer text, date, page numbers etc. values for all pages. 8. Check if the data displayed on a page and exported Excel file is the same. 9. Check export functionality when pagination is enabled. 10. Check if export button is showing proper icon according to the exported file type E.g . Excel file icon for xls files 11. ...
Post a Comment
Read more

Software Testing Tips

Here are some of the Best Testing Practices which I learned by Experience:  1) Learn to analyze your test results thoroughly. Do not ignore any test result. The final test result may be ‘pass’ or ‘fail’, but troubleshooting the root cause of ‘fail’ will give you the solution of the problem. Testers will be respected if they not only log the bugs but also provide solutions. 2) Learn to maximize the test coverage each time you test any application. 100% test coverage might not be possible but still, you can always try to reach near it. 3) In order to ensure maximum test coverage, break your application under test (AUT), into smaller functional modules. Write test cases on such individual unit modules. Also if possible break these modules into smaller parts. E.g : Lets assume that you have divided your website application in modules and ‘accepting user information’ is one of the modules. You can break this ‘User information’ screen into smaller parts for writing ...
Post a Comment
Read more