Custom Search

Thursday, September 3, 2009

Test Partner

TestPartner - Introduction

IT managers charged with ensuring application quality are confronted with a number of critical business challenges:

  • Verify that applications function as expected and fulfill business requirements

  • Test multiple heterogeneous application technologies

  • Meet ever-more-rapid release schedules

  • Achieve the right balance between risk and quality.

If that weren't enough, IT struggles with limited resources, hard deadlines that squeeze testing cycles and late-breaking requirement changes.

In the face of these business demands, TestPartner's functional testing capabilities accelerate testing and enable successful application delivery outcomes on-time, at a lower cost, with higher quality than ever before. TestPartner achieves these results through a tiered approach to testing that enables developers, quality experts, and non-technical application users to collaborate and test more in the time available.

TestPartner's visual, contextual approach to capturing business processes empowers non-technical application users to participate in the testing process. At the same time, TestPartner provides expert testers and software developers with access to Visual Basic for Applications, allowing them to solve even the most complex testing challenges. This flexibility and focus on usability allows quality teams to produce positive results even with minimal training.

TestPartner enables IT to:



  1. Leverage non-technical as well as experienced testers to test applications more thoroughly in the time available

  2. Collaborate throughout the software development lifecycle, resulting in higher team efficiency and greater project effectiveness

  3. Automate regression testing to quicken acceptance of application patches, service packs, and other regular updates

  4. Clearly and unambiguously document test results, accelerating the identification and resolution of application issues

  5. Understand the results of testing, enabling confident delivery of applications that meet requirements and provide the expected business value

  6. Use test results to facilitate test maintenance, providing improved return on the test automation investment
  7. Build quality into applications earlier in the life cycle, leading to lower development and maintenance costs

  8. Accelerate quality efforts for a broad range of technology platforms, including Web, .NET, Java, SAP, Oracle and many other distributed Windows-based applications.

TestPartner's value is further enhanced through its tight integration with Compuware's Test Management solution, which improves application delivery by providing IT with the ability to more effectively assess and balance risk, cost, and schedule. TestPartner is also an integral component within Quality Management, which provides IT with the ability to control, measure, manage and continuously improve the delivery of higher quality applications. Quality Management's reporting and real-time insight into project quality status results in informed quality decisions, and allows IT to deploy applications with greater confidence.


TestPartner - Product Preview

Automated, repeatable testing with TestPartner TestPartner is an automated testing tool that accelerates functional testing and facilitates the delivery of business-critical applications.

With TestPartner, you can more rapidly validate applications before going live, verify that application updates don't introduce regressions or even test nightly builds with automated smoke tests. TestPartner offers a storyboard-based visual approach to testing that lets application users confidently capture test scenarios. VBA scripting is available to enable advanced users to meet even the most demanding test cases. You build test assets earlier in the development life cycle, test more thoroughly and deploy applications with confidence.

TestPartner's broad environment support means that enterprises with heterogeneous environments can be confident about easily validating Microsoft, Java, web, SAP, Oracle and many other distributed technologies with speed and consistency.


TestPartner - Build tests without programming

Unlike testing tools that require users to understand a programming language, TestPartner's Visual Navigator makes testing accessible to even novice users, allowing virtually anyone to be immediately productive.


TestPartner - Build tests without programming

Unlike testing tools that require users to understand a programming language, TestPartner's Visual Navigator makes testing accessible to even novice users, allowing virtually anyone to be immediately productive.

Within the Visual Navigator, you access panes that provide a preview of each screen being tested, the pertinent test steps for each and a storyboard view that ties it all together. As each step is selected, the corresponding control within the screen preview is highlighted, which clearly defines the automation context.
Additionally, each test step has related properties that can be modified by the user or even populated via a data file to facilitate fully data-driven testing. Ultimately, this approach allows application users—who are intimately familiar with the application under test, but often lack the technical expertise to use automated testing tools—to comfortably and confidently capture business transactions, verify the proper functionality is tested and assist in updating the test when inaccuracies are found or the application changes.


TestPartner - Modify and customize tests

In addition to capturing a screenshot of each application window, which is displayed within the screen preview pane,

TestPartner records detailed information about the controls and properties for each screen. This means you can easily augment or modify an existing test based upon the information already captured.

For example, you can:



  • insert new steps directly from the screen preview (or the application under test)

  • modify existing tests to perform different or additional steps
  • change the action performed (e.g., replace single-click with a double-click) or the data being input

  • add verifications that weren't inserted during the initial record session

  • do all of this without having to re-record against the original application.

This "offline editing" capability is especially valuable for modern "workflow-driven" applications

, where you might spend several minutes or more simply returning to the point where you can capture additional data or record new actions. With TestPartner, as long as the underlying application data hasn't changed, you achieve higher productivity by simply going right to the pertinent screen and making changes and additions as needed.


TestPartner - Understand and document tests and results unambiguously

TestPartner removes abstraction to give users a better understanding of what the test should automate and the actual results. You no longer have to guess. You can see exactly what each step intends to automate.


Similarly, when a test exposes an application problem, the visual test results are much more efficient and effective in leading to a positive identification and resolution. You no longer have to struggle for hours to reproduce issues live.

Additionally, tests can be printed to provide external documents for manual testing, user documentation and training, or archived for process compliance and auditing. Similarly, test results can be printed to provide reports that can be reviewed at meetings, aid with troubleshooting or provide evidence supporting process compliance.


TestPartner - Build in test "intelligence" with logic designers

To test applications thoroughly, it's important to do more than simply record and playback.

TestPartner comes with built-in wizards and logic designers that make it easy to build and execute sophisticated test cases.

These wizards and logic designers are instantly accessible through the Logic Toolbox or via right-click menus. Users can successfully fulfill even complex test cases by adding logic that allows:

  1. quick creation of data-driven tests

  2. testing for the presence of text, images, properties, etc.

  3. steps to occur only when specific conditions are met

  4. creation and use of variable data

  5. repetition of test steps

  6. testing and verification of actual and expected results

  7. synchronization of the test with the application being tested

  8. automatic error handling

  9. and more.

TestPartner - Accelerate test maintenance

One of the biggest challenges with automated testing is maintaining the test assets over time.

When the application changes, the test cases that correspond to that functionality need to be updated. TestPartner simplifies this effort in two ways.

First, you can view results with the Visual Navigator, TestPartner's built-in screen preview that shows both the original test screen and the screen that was captured at playback, allowing you to identify critical changes in the application immediately.

Second, TestPartner's one-click Update Screen feature allows application changes to be instantly captured into the visual test. For example, if you determined that a new field was added to an existing screen within the application under test, you could select the Update Screen to capture the new screen definition (along with associated properties) without having to re-record the test. By enabling you to spend less time on test maintenance and more time on testing the application thoroughly, TestPartner improves your return on investment.


TestPartner - VBA scripting

TestPartner's visual tests provide an approach to testing that requires no programming experience, and offers more advanced capabilities for expert users via Microsoft Visual Basic for Applications.


The availability of VBA-based tests means expert users can work at whatever level is best suited for a given project or test—use an entirely visual approach, integrate VBA routines with visual tests to enable customization and complex text cases, or work entirely with VBA.


TestPartner's VBA and visual testing features are designed to work closely in conjunction, so testers can call VBA routines at any point within a visual test, passing and returning data as necessary to fulfill the test case.VBA's rich feature-set, which includes broad debugging capabilities and Microsoft auto-completing IntelliSense™, makes users more efficient and productive than with proprietary programming languages or other feature-poor development environments.


TestPartner - VBA scripting

TestPartner's visual tests provide an approach to testing that requires no programming experience, and offers more advanced capabilities for expert users via Microsoft Visual Basic for Applications.


The availability of VBA-based tests means expert users can work at whatever level is best suited for a given project or test—use an entirely visual approach, integrate VBA routines with visual tests to enable customization and complex text cases, or work entirely with VBA.


TestPartner's VBA and visual testing features are designed to work closely in conjunction, so testers can call VBA routines at any point within a visual test, passing and returning data as necessary to fulfill the test case.VBA's rich feature-set, which includes broad debugging capabilities and Microsoft auto-completing IntelliSense™, makes users more efficient and productive than with proprietary programming languages or other feature-poor development environments.


TestPartner - Collaborate to communicate and operate more effectively

As test teams get increasingly distributed and incorporate application users, testers and developers, clear and effective communication becomes increasingly important.

To that end, TestPartner includes a team-oriented collaboration feature that allows users to flag and describe particular items of interest within a test or test result, and assign to another user as applicable. This allows work scenarios where, for example:

  1. An application user successfully captures a business process, and then flags and assigns it to a quality expert for inclusion within the test framework.

  2. A member of the quality team reproduces a defect, flags the point at which the problem occurs and assigns it to a developer for investigation.

  3. The test result appears to show a change in the application under test. A member of the quality team assigns the result to an application user to verify whether this is the expected behavior.

TestPartner Program

Transition Networks's Test Partner Program is a new kind of product testing program.

The Test Partner Program consists of our Technical Support staff and select Transition customers working together to insure that product supportability is designed into every Transition product. We do this by providing our Test Partner Program participants with final releases of products, and then working closely with the Test Partner to find ways to enhance/improve the product.

Through Test Partners, Transition is able to isolate and resolve a problem, or define and determine the scope of a new feature or function, resulting in a win-win situation for Transition, our resellers and our customers.

Test Partners are not expected to execute a laborious product acceptance test plan. We recognize that a Test Partner's resources may be limited. Test Partners can test the product any way they want to. The challenge is simple - break it if you can. We promise that all problems reported by a Test Partner will be Priority #1!

Our Technical Support Department qualifies potential Test Partners on the basis of robustness of their networks, client count, eagerness to participate in the program, and the networking expertise of the Test Partner's technical contact person. Most importantly, the Test Partner must possess a "partner", rather than a "customer" mentality.

Transition's Test Partner Program requirements are few, but important. Participants must:

  1. provide a diagram of their network illustrating backbones, device and client count.

  2. capture a performance baseline before installation so that a comparison can be made.

  3. give this testing a reasonable amount of priority.

  4. provide as much detail as practical when reporting problems.

  5. allow Transition's Marketing Department an interview so that the prestige of their opinion can be shared.

Events

Events are unscheduled occurrences or conditions to which you want the target application to respond in a specified manner. Test Partner supports two categories of events: Wait and Whenever.

A Wait event tells Test Partner to wait for a specified occurrence before proceeding. Wait events are useful in situations where you cannot anticipate the amount of time a response will take. An example of a Wait event would be waiting for a system login prompt. When your script is running against a network-based application that requires the user

to log in, the amount of time it takes for the login prompt to display may vary. To account for this variance, you can insert a Wait event that instructs your script to wait for the login prompt before proceeding to type a username and password.

A Whenever event tells Test Partner to watch for a specific occurrence and, if it occurs, perform a special set of steps. Whenever events are useful for trapping unexpected error conditions during a test run. For example, you can include events in your scripts to recognize when the connection to the server has been interrupted by a communications error or a network system message has been received, so that the script can report or work around the problem. In a script, Test Partner automatically inserts the Script_Whenever function by default to handle the whenever event. If a whenever event is inserted into a module, shared module, or class module, you must customize the whenever event handler code. Test Partner supports the following types of Events:

i) Bitmap Event:--

A bitmap event detects the presence, absence, or state of a graphic in a window.

ii) Date/Time Event:--

date/Time events enable you to define a date or time condition. Test Partner recognizes the event by monitoring the internal clock of the computer on which it and the target application are running.

iii) Key Event:--

Watch for the entry of a particular keystroke combination by the user. You can use key events to:

  • Build your own “hotkeys” to make Test Partner perform an action whenever the hotkey is used.
  • Interrupt a script to take manual control of the target application.
  • Pause a script until a particular key is used.
  • Prevent certain keys from being entered.
iv) Menu Events:--

Watch for when a particular menu item is selected by the user.

v) Mouse Events:--

Watch for when one of the mouse buttons is clicked or released in a certain window.

vi) Screen Events:--

A screen event detects the presence or absence of text in a window. The most common use of screen events is to synchronize with host-based applications and to detect error messages.

vii) Window Events:--

A window event detects an action on a window; for example, its creation, destruction, movement, or its existence.

Data Driven Test:--

The Test Partner Active Data Test Creation wizard provides a non-programmatic way to create data-driven tests. Such tests are useful for testing form-based applications. Using the wizard, you can record a test, choose the fields you want to include in your data file, then populate the data file itself using a data table.

To create a data test

1. From the Script menu, choose Create Data Test. The Data Test wizard appears.
2. Read the instructions and click Next.
3. Follow the instructions in the Data Layout Assistant for the three steps necessary to define the scope of the test.
4. Enter a name for the Data Table.
5. Exclude any fields you do not want to include in the test by unchecking the Use checkbox and click Next.
6. Read the instructions and click Finish.


TestPartner shows the Data Table, which includes a column for each field you defined and one row of data. The data table also includes a column labelled Results Script, to specify a script to be run after the data driven test.


To modify the data table.

1. If you have just recorded a new data test and the data table is open, proceed to step 3.


2. To modify an existing data test, select Modify Data Table on the Script menu and choose the data table you want to change.


3. To add rows and populate the table with test data, right-click on the empty row labelled END ( or any other row) and select Insert on the context menu. Test Partner inserts a new row above the selected row.


4. Enter test data into the cells of the new row.


5. Alternatively, right-click the empty row and choose Import. You can import data from a tab-delimited text (.TXT) or comma-delimited (.CSV) file to populate the cells of the data table. If you select the END row in the table, TestPartner will add multiple rows if needed to accommodate the data.


6. To delete rows from the table, right-click the row and choose Delete. To delete multiple rows, press the Ctrl or Shift (for contiguous rows) key while selecting rows to delete.


7. To launch another script from the data test, insert the name of the script in the Results Script field in the table at any point(s) at which you want to run the script.


8. When you have finished editing the data table, click Save and Close to exit.




Friday, August 14, 2009

Costly Software Bugs


Software Bugs Cost U.S. Economy $59.6 Billion Annually, RTI Study Finds
Research Triangle Park, NC -- Software bugs are costly both to software producers and users.
Extrapolating from estimates of the costs in several software-intensive industries, bugs may be
costing the U.S. economy $59.5 billion a year; about 0.6 percent of gross domestic product, says a
study conducted by RTI for the U.S. Department of Commerce's National Institute of Standards and
Technology (NIST).

"More than half of the costs are borne by software users, and the remainder by software developers
and vendors," NIST said in summarizing the findings. "More than a third of these costs … could be
eliminated by an improved testing infrastructure that enables earlier and more effective identification
and removal of software defects."


History's Worst Software Bugs

What seems certain is that bugs are here to stay. Here, in chronological order, is the Wired News list
of the 10 worst software bugs of all time … so far.

July 28, 1962 -- Mariner I space probe. A bug in the flight software for the Mariner 1 causes the
rocket to divert from its intended path on launch. Mission control destroys the rocket over the
Atlantic Ocean. The investigation into the accident discovers that a formula written on paper in
pencil was improperly transcribed into computer code, causing the computer to miscalculate the
rocket's trajectory.

1982 -- Soviet gas pipeline. Operatives working for the Central Intelligence Agency allegedly (.pdf)
plant a bug in a Canadian computer system purchased to control the trans-Siberian gas pipeline.
The Soviets had obtained the system as part of a wide-ranging effort to covertly purchase or steal
sensitive U.S. technology. The CIA reportedly found out about the program and decided to make it
backfire with equipment that would pass Soviet inspection and then fail once in operation. The
resulting event is reportedly the largest non-nuclear explosion in the planet's history.

1985-1987 -- Therac-25 medical accelerator. A radiation therapy device malfunctions and delivers
lethal radiation doses at several medical facilities. Based upon a previous design, the Therac-25 was
an "improved" therapy system that could deliver two different kinds of radiation: either a low-power
electron beam (beta particles) or X-rays. The Therac-25's X-rays were generated by smashing high-
power electrons into a metal target positioned between the electron gun and the patient. A second
"improvement" was the replacement of the older Therac-20's electromechanical safety interlocks with
software control, a decision made because software was perceived to be more reliable.

What engineers didn't know was that both the 20 and the 25 were built upon an operating system
that had been kludged together by a programmer with no formal training. Because of a subtle bug
called a "race condition," a quick-fingered typist could accidentally configure the Therac-25 so the
electron beam would fire in high-power mode but with the metal X-ray target out of position.
At least five patients die; others are seriously injured.



1988 -- Buffer overflow in Berkeley Unix finger daemon. The first internet worm (the so-called
Morris Worm) infects between 2,000 and 6,000 computers in less than a day by taking advantage
of a buffer overflow. The specific code is a function in the standard input/output library routine called
gets() designed to get a line of text over the network. Unfortunately, gets() has no provision to limit
its input, and an overly large input allows the worm to take over any machine to which it can connect.

Programmers respond by attempting to stamp out the gets() function in working code, but they
refuse to remove it from the C programming language's standard input/output library, where it remains
to this day.

1988-1996 -- Kerberos Random Number Generator. The authors of the Kerberos security system
neglect to properly "seed" the program's random number generator with a truly random seed. As a
result, for eight years it is possible to trivially break into any computer that relies on Kerberos for
authentication. It is unknown if this bug was ever actually exploited.

January 15, 1990 -- AT&T Network Outage. A bug in a new release of the software that controls
AT&T's #4ESS long distance switches causes these mammoth computers to crash when they receive
a specific message from one of their neighboring machines -- a message that the neighbors send out
when they recover from a crash.

One day a switch in New York crashes and reboots, causing its neighboring switches to crash, then
their neighbors' neighbors, and so on. Soon, 114 switches are crashing and rebooting every six
seconds, leaving an estimated 60 thousand people without long distance service for nine hours. The
fix: engineers load the previous software release.

1993 -- Intel Pentium floating point divide. A silicon error causes Intel's highly promoted Pentium
chip to make mistakes when dividing floating-point numbers that occur within a specific range. For
example, dividing 4195835.0/3145727.0 yields 1.33374 instead of 1.33382, an error of 0.006 percent.
Although the bug affects few users, it becomes a public relations nightmare. With an estimated 3
million to 5 million defective chips in circulation, at first Intel only offers to replace Pentium chips for
consumers who can prove that they need high accuracy; eventually the company relents and agrees
to replace the chips for anyone who complains. The bug ultimately costs Intel $475 million.


1995/1996 -- The Ping of Death. A lack of sanity checks and error handling in the IP fragmentation
reassembly code makes it possible to crash a wide variety of operating systems by sending a
malformed "ping" packet from anywhere on the internet. Most obviously affected are computers
running Windows, which lock up and display the so-called "blue screen of death" when they receive
these packets. But the attack also affects many Macintosh and Unix systems as well.

June 4, 1996 -- Ariane 5 Flight 501. Working code for the Ariane 4 rocket is reused in the Ariane 5,
but the Ariane 5's faster engines trigger a bug in an arithmetic routine inside the rocket's flight
computer. The error is in the code that converts a 64-bit floating-point number to a 16-bit signed
integer. The faster engines cause the 64-bit numbers to be larger in the Ariane 5 than in the Ariane
4, triggering an overflow condition that results in the flight computer crashing.

First Flight 501's backup computer crashes, followed 0.05 seconds later by a crash of the primary
computer. As a result of these crashed computers, the rocket's primary processor overpowers the
rocket's engines and causes the rocket to disintegrate 40 seconds after launch.

November 2000 -- National Cancer Institute, Panama City. In a series of accidents, therapy
planning software created by Multidata Systems International, a U.S. firm, miscalculates the proper
dosage of radiation for patients undergoing radiation therapy.

Multidata's software allows a radiation therapist to draw on a computer screen the placement of
metal shields called "blocks" designed to protect healthy tissue from the radiation. But the software
will only allow technicians to use four shielding blocks, and the Panamanian doctors wish to use five.

The doctors discover that they can trick the software by drawing all five blocks as a single large
block with a hole in the middle. What the doctors don't realize is that the Multidata software gives
different answers in this configuration depending on how the hole is drawn: draw it in one direction
and the correct dose is calculated, draw in another direction and the software recommends twice
the necessary exposure.

At least eight patients die, while another 20 receive overdoses likely to cause significant health
problems. The physicians, who were legally required to double-check the computer's calculations
by hand, are indicted for murder.

Monday, August 10, 2009

Code Coverage - Typical features

he feature sets, quality and usability of code coverage products vary significantly.
  • Ant integration

    Probably most Java projects today are using Ant (or Maven) to manage their build process, including running unit tests (or functional tests).

    Thus, Ant integration is one of those features a code coverage tool cannot afford not to have. However, there are subtle differences in how nicely the code coverage related targets fit into an existing build script. Yes, we will see some examples later on. Of course, most tools also provide an alternative, standalone way of running the analysis, either from the command line or via a GUI application.

  • Report formats

    Another obvious feature a code coverage tool must have is reports. Again, there are differences in the type and quality of supported reports. Some tools provide only textual summaries in Ant console output, others produce huge tables of names and numbers in HTML, and others produce nice pictures, others offer to render all this in PDF as well. We'll see examples of the main types of reports in the next section.

  • Source code linking

    Somewhat related to the previous item, source code linking is something one can't live without once having gotten the taste of it. In practice, source code linking means that, as a part of the code coverage report, the tool has generated annotated copies of the actual source code, highlighting the parts which are not covered by your tests. I wouldn't be surprised if this particular feature was the single biggest benefactor in code coverage tools reaching critical mass. Seeing the code block that is causing your coverage to stay away from the "green" is a lot more efficient than seeing that a particular method contains some code that isn't covered by the tests. All of our selected examples include source code linking in their feature set.

  • Checks

    It doesn't take too long after someone has introduced a rule when someone else introduced the idea to enforce that rule. That has also happened to code coverage. Some tools provide a means to pull up the red flag if code coverage drops below a given level. In the context of Ant integration, the build script might typically fail the build until the tests have been reinforced to cover the naked parts of the code.

  • Historical reports

    Few tools provide a way to collect a history of coverage data and produce historical reports illustrating how your project's code coverage has been fluctuating in the course of time. This is also a nice feature, although some might consider it rather irrelevant.

Thursday, August 6, 2009

Testing Estimation Process

Introduction

In my opinion, one of the most difficult and critical activities in IT is the estimation process. I believe that it occurs because when we say that one project will be accomplished in such time by at such cost, it must happen.

If it does not happen, several things may follow: from peers' comments and senior management's warnings to being fired depending on the reasons and seriousness of the failure.

Before even thinking of moving to Systems test at my organization, I always heard from the development group members that the estimations made by the Systems test group were too long and expensive. Then, when I arrived at my new seat, I tried to understand the testing estimation process.

The testing estimation process in place was quite simple. The inputs for the process, provided by the development team, were: the size of the development team and the number of working days needed for building a solution before starting systems tests.

The testing estimation process said that the number of testing engineers would be half of the number of development engineers and one third of the number of development working days.

A spreadsheet was created in order to find out the estimation and calculate the duration of tests and testing costs. They are based on the following formulas:

Testing working days = (Development working days) / 3.

Testing engineers = (Development engineers) / 2.

Testing costs = Testing working days * Testing engineers * person daily costs.

As the process was only playing with numbers, it was not necessary to register anywhere how the estimation was obtained.

To exemplify how the process worked, if one development team said that to deliver a solution for systems testing it would need 4 engineers and 66 working days then, the systems test would need 2 engineers (half) and 21 working days (one third). So, the solution would be ready for delivery to the customer after 87 (66+21) working days.

Just to be clear, in testing time, it was not included the time for developing the testcases and preparing the testing environment. Normally, it would need an extra 10 days for the testing team.


The Rules



1st Rule: Estimation shall be always based on the software requirements

All estimation should be based on what would be tested, i.e., the software requirements.

Normally, the software requirements were only established by the development team without any or just a little participation from the testing team. After the specification have been established and the project costs and duration have been estimated, the development team asks how long would take for testing the solution. The answer should be said almost right away. Then, the software requirements shall be read and understood by the testing team, too. Without the testing participation, no serious estimation can be considered.


2nd Rule: Estimation shall be based on expert judgment

Before estimating, the testing team classifies the requirements in the following categories:

" Critical: The development team has little knowledge in how to implement it;

" High: The development team has good knowledge in how to implement it but it is not an easy task;

" Normal: The development team has good knowledge in how to implement.

The experts in each requirement should say how long it would take for testing them. The categories would help the experts in estimating the effort for testing the requirements.


3rd Rule: Estimation shall be based on previous projects

All estimation should be based on previous projects. If a new project has similar requirements from a previous one, the estimation is based on that project.



4th Rule: Estimation shall be based on metrics

My organization has created an OPD, Organization Process Database, where the project metrics are recorded. We have recorded metrics from three years ago obtained from dozens of projects.

The number of requirements is the basic information for estimating a testing project. From it, my organization has metrics that guide us to estimate a testing project. The table below shows the metrics used to estimate a testing project. The team size is 01 testing engineer.


Metric Value

1.Number of testcases created for each requirement 4,53

2.Number of testcases developed by Working day 14,47

3.Number of testcases executed by Working day 10,20

4.Number of ARs for testcase 0,77

5.Number of ARs verified by Working day 24,64

For instance, if we have a project with 70 functional requirements and a testing team size of 2 engineers, we reach the following estimates:


Metric Value

Number of testcases - based on metric 1 317,10

Preparation phase - based on metric 2 11 working days

Execution phase - based on metric 3 16 working days

Number of ARs - based on metric 4 244 ARs

Regression phase - based on metric 5 6 working days

The testing duration is estimated in 22 (16+6) working days. Plus, 11 working days for preparing it.


5th Rule: Estimation shall never forget the past

I have not sent away the past. The testing team continues using the old process and the spreadsheet. After the estimation is done following the new rules, the testing team estimates again using the old process in order to compare both results.

Normally, the results from the new estimate process are cheaper and faster than the old one in about 20 to 25%. If the testing team gets a different percentage, the testing team returns to the process in order to understand if something was missed.


6th Rule: Estimation shall be recorded

All decisions should be recorded. It is very important because if requirements change for any reason, the records would help the testing team to estimate again. The testing team would not need to return for all steps and take the same decisions again. Sometimes, it is an opportunity to adjust the estimation made earlier.


7th Rule: Estimation shall be supported by tools

A new spreadsheet has been created containing metrics that help to reach the estimation quickly. The spreadsheet calculates automatically the costs and duration for each testing phase.

There is also a letter template that contains some sections such as: cost table, risks, and free notes to be filled out. This letter is sent to the customer. It also shows the different options for testing that can help the customer decides which kind of test he needs.


8th Rule: Estimation shall always be verified

Finally, All estimation should be verified. I've created another spreadsheet for recording the estimations. The estimation is compared to the previous ones recorded in a spreadsheet to see if they have similar trend. If the estimation has any deviation from the recorded ones, then a re-estimation should be made.



Tuesday, July 28, 2009

Test Matices Sample

You can measure the arrival and departure times of developers, if you have them clock in, but that won't tell you much since not all work is done in the office (and it doesn't mean that they're working when they're in the office). This is, however, still a metric.

The same holds for a true "quality metric". The most familiar one is defects per thousand lines of (uncommented) code. But this metric assumes that:
1) you count the lines of code
2) the complexity of the code isn't an issue
3) the programmers aren't playing games (like using continuance characters
so that what could have been written in one line isn't done in five lines)
4) all defects are uncovered in the code in a single pass
5) each defect discovered is all others
6) defects are uncovered in a linear manner between revisions or builds

The fact is that first you need to know what your goal is. Then you need to
discover or create a metric that will help you achieve that goal. Then you
need to implement it and be prepared to adjust it.

You can't use measurements (metrics) to find faults, at least not in software, so that's not a reasonable goal. You can use metrics to help determine if most of the defects have been discovered already. You can use them to tell you how much longer it will take to uncover a reasonable amount of defects. For either of these metrics you will need to know how previous projects of similar size and complexity (using similar languages, etc.) were done in order to get a reasonable comparison.


Posted by Walter Gorlitz

Test Case: File Open #

Test
Description

Test Cases/ Samples

Pass/
Fail

No. of
Bugs

Bug#

Comments

N/A

Setup for [Product Name] setup

-

-

-

1.1

Test that file types supported by the program can be opened

1.1

P/F

#

#

1.2

Verify all the different ways to open file (mouse, keyboard and accelerated keys)

1.2

P/F

#

#

1.3

Verify files can be open from the local drives as well as network

1.3

P/F

#

#




NOTE: This is only a sample of a Test Matrices based on editor application. In real environments your Case's contents and layout most likely will be different, depends on your project and company requirements.