The International Institute for Software Testing is
giving away FIFTY days of free training.
Up to TEN companies may win. Each company will get Five
days of free training.
Apply for the IIST's Software Testing Best Practice Award
at http://www.iist.org/bestpractice and receive the following benefits:
**** Get your company featured as an Award Winning Company
In all IIST publicity channels and press releases
**** Tell everyone how great your test process is
**** Get 5 days of free training at the International
Testing Certification Super Week to be held in
Las Vegas, NV, November 26-30, 2007
Chicago, IL, March 24-28, 2008
See details at http://iist.org/superweek
**** Get your company and your test team recognized and identified
as an Award Winning Team during these remarkable events
The International Testing Certification Super Week will be
held in the following cities:
Las Vegas, NV, November 26-30, 2007
Chicago, IL, March 24-28, 2008
During these events, IIST will offer 25 Full day
in-depth courses taught by Leading Industry Experts
in Software Testing & Quality.
**** Register by September 30th, and save 20% (Las Vegas)
See details at: http://www.iist.org/stpw/lasvegas/index.php
**** Register by December 31st, 2007 and save 30% (Chicago)
See details at: http://www.iist.org/stpw/chicago08/index.php
Saturday, February 23, 2008
Software Testing Best Practice Award
Reporting bugs - A how to guide
http://www.edgeofmyseat.com/articles/2007/07/08/reporting-bugs/
Full Text of the article
-----------------------------------------------------
When working with a developer or team of developers on an application – whether you are a designer working with developers or an end client hiring developers – you all want the same end result, a slick and bug free application. During the testing process of any application it is likely that some bugs or issues will show up and this article aims to explain how to report bugs and problems effectively so that your developers don’t need to spend time working out what the problem is before being able to fix it. This helps to ensure that projects stay on budget and that developers are spending their time adding features to the application rather than trying to get enough details to be able to reproduce and fix issues.
“It’s just not working!”
When you find a problem, it is very tempting to just fire off an email and presume that the developer will immediately be able to see the problem too. However, by taking a few minutes to describe the problem you have encountered accurately you can prevent any confusion occurring as to what the problem is and save both your time and the developer’s as she won’t need to get back to you to find out what actually happened, or spend a long time trying to reproduce the issue.
A good report
A good bug report tells your developer three vital things:
- What you expected to happen
- What actually happened
- What you did/were doing when it happened
What you expected to happen
There are two kinds of ‘bugs’, the first is where something breaks – you see an error message, your uploaded data disappears, you submit a form and the change isn’t saved. These bugs are generally pretty easy to report and identify as all your developer needs is to know exactly what you were doing or inputting at the time and they should be able to reproduce and fix the issue.
The second kind of bug is where the application doesn’t function as you expected. This might be because the developer has misinterpreted part of the specification or it could be that what you expect just isn’t how something can work. In this case the developer believes that it is working fine – and in fact it is ‘working’ even if it is incorrect. If your bug report is that the feature is broken, the developer may then spend time looking for some error in this part of the application when what they need to realize is that it isn’t working as you expected. By giving the information about what you expected to happen the developer can think ‘ah … you wanted it to do x and it is doing y’ and a resolution can be sorted out quickly.
What actually happened
What actually happened is very rarely ‘nothing’ yet bug reports often contain the phrase, ‘nothing happened’. If what happened was ‘nothing’ in terms of the intended result then explain that in a few more words, for example, if you clicked the submit button on a form and it didn’t submit and go onto the next page you could say,
“The form didn’t submit – it just remained on the same page.”
Or perhaps the form submitted and a blank page displayed,
“After submitting the form a blank page loaded.”
If an error message displays on the screen then include that in the report. Just copy and paste the error message.
If you use Internet Explorer then your browser may not display the error message generated by the server, instead showing a generic error page. You can ensure the IE displays the real error message by going to Tools > Internet Options > Advanced. Then scroll down to the browsing section and uncheck ‘Show Friendly HTTP error messages’.
What you were doing when it happened
Your developer wants to know this information – not because they want to tell you that you were doing something wrong, but because it is highly likely that the bug occurs only when a certain path of actions is followed, or when a certain type of data is entered. The more information you can give your developer the easier it will be for them to reproduce the problem you saw and fix it. Things you should include:
The steps taken
List exactly what you did, in the order you did it if possible. If you can go back and try the same steps again and the problem happens again that is great – note down exactly how you made the problem occur. Your developer will be pleased as you have just saved her time trying to reproduce the issue. Even if you can’t reproduce it, no-one is going to doubt that the problem happened – just describe as much as you can remember how you got to the broken point.
Any data you were entering
If the problem happened after you added some data to a form, include the data with the bug report. If you were uploading something such as an image into the application then include that too.
It may also be helpful to copy and paste the URL out of the address bar of the browser so the developer knows exactly which page you were on at the time.
The browser and operating system you were using at the time
With web applications problems may only be occurring in one browser. Let your developer know exactly what you are using – including the version number - so they can create the same environment to test the problem.
Effective bug reporting can make a huge difference in how quickly problems can be resolved, and prevent frustration on both sides of the process. Including the above information, even if it doesn’t seem relevant, will be appreciated by the developer. You don’t need to write an essay, just a few clear lines explaining the key information of:
- what you expected to happen
- what actually happened and,
- what you did/were doing when it happened.
This will be enough to isolate all but the most complicated of issues, and once an issue can be reproduced it is well on its way to being fixed.
Requirements Testing
Testing software is an integral part of building a system. However, if the software is based on inaccurate requirements, then despite well written code, the software will be unsatisfactory. Most of the defects in a system can be traced back to wrong, missing, vague or incomplete requirements.
Requirements seem to be ephemeral. They flit in and out of projects, they are capricious, intractable, unpredictable and sometimes invisible. When gathering requirements we are searching for all of the criteria for a system's success. We throw out a net and try to capture all these criteria.
The Quality Gateway
As soon as we have a single requirement in our net we can start testing. The aim is to trap requirements-related defects as early as they can be identified. We prevent incorrect requirements from being incorporated in the design and implementation where they will be more difficult and expensive to find and correct.
To pass through the quality gateway and be included in the requirements specification, a requirement must pass a number of tests. These tests are concerned with ensuring that the requirements are accurate, and do not cause problems by being unsuitable for the design and implementation stages later in the project.
Make The Requirement Measurable
In his work on specifying the requirements for buildings, Christopher Alexander describes setting up a quality measure for each requirement.
"The idea is for each requirement to have a quality measure that makes it possible to divide all solutions to the requirement into two classes: those for which we agree that they fit the requirement and those for which we agree that they do not fit the requirement."
In other words, if we specify a quality measure for a requirement, we mean that any solution that meets this measure will be acceptable. Of course it is also true to say that any solution that does not meet the measure will not be acceptable.
The quality measures will be used to test the new system against the requirements. The remainder of this paper describes how to arrive at a quality measure that is acceptable to all the stakeholders.
Quantifiable Requirements
Consider a requirement that says "The system must respond quickly to customer enquiries". First we need to find a property of this requirement that provides us with a scale for measurement within the context. Let's say that we agree that we will measure the response using minutes. To find the quality measure we ask: "under what circumstances would the system fail to meet this requirement?" The stakeholders review the context of the system and decide that they would consider it a failure if a customer has to wait longer than three minutes for a response to his enquiry. Thus "three minutes" becomes the quality measure for this requirement.
Any solution to the requirement is tested against the quality measure. If the solution makes a customer wait for longer than three minutes then it does not fit the requirement. So far so good: we have defined a quantifiable quality measure. But specifying the quality measure is not always so straightforward. What about requirements that do not have an obvious scale?
Non-quantifiable Requirements
Suppose a requirement is "The automated interfaces of the system must be easy to learn". There is no obvious measurement scale for "easy to learn". However if we investigate the meaning of the requirement within the particular context, we can set communicable limits for measuring the requirement.
Again we can make use of the question: "What is considered a failure to meet this requirement?" Perhaps the stakeholders agree that there will often be novice users, and the stakeholders want novices to be productive within half an hour. We can define the quality measure to say "a novice user must be able to learn to successfully complete a customer order transaction within 30 minutes of first using the system". This becomes a quality measure provided a group of experts within this context is able to test whether the solution does or does not meet the requirement.
An attempt to define the quality measure for a requirement helps to rationalise fuzzy requirements. Something like "the system must provide good value" is an example of a requirement that everyone would agree with, but each person has his own meaning. By investigating the scale that must be used to measure "good value" we identify the diverse meanings.
Sometimes by causing the stakeholders to think about the requirement we can define an agreed quality measure. In other cases we discover that there is no agreement on a quality measure. Then we substitute this vague requirement with several requirements, each with its own quality measure.
Requirements Test 1
Does each requirement have a quality measure that can be used to test whether any solution meets the requirement?
By adding a quality measure to each requirement we have made the requirement visible. This is the first step to defining all the criteria for measuring the goodness of the solution. Now let's look at other aspects of the requirement that we can test before deciding to include it in the requirements specification.
Requirements Test 2
Does the specification contain a definition of the meaning of every essential subject matter term within the specification?
When the allowable values for each of the attributes are defined it provides data that can be used to test the implementation.
Requirements Test 3
Is every reference to a defined term consistent with its definition?
Requirements Test 4
Is the context of the requirements wide enough to cover everything we need to understand?
Requirements Test 5
Have we asked the stakeholders about conscious, unconscious and undreamed of requirements?
Requirements Test 5 (enlarged)
Have we asked the stakeholders about conscious, unconscious and undreamed of requirements? Can you show that a modelling effort has taken place to discover the unconscious requirements? Can you demonstrate that brainstorming or similar efforts taken place to find the undreamed of requirements?
Requirements Test 6
Is every requirement in the specification relevant to this system?
Requirements Test 7
Does the specification contain solutions posturing as requirements?
Requirements Test 8
Is the stakeholder value defined for each requirement?
Requirements Test 9
Is each requirement uniquely identifiable?
Requirements Test 10
Is each requirement tagged to all parts of the system where it is used? For any change to requirements, can you identify all parts of the system where this change has an effect?
Conclusions
The requirements specification must contain all the requirements that are to be solved by our system. The specification should objectively specify everything our system must do and the conditions under which it must perform. Management of the number and complexity of the requirements is one part of the task.
The most challenging aspect of requirements gathering is communicating with the people who are supplying the requirements. If we have a consistent way of recording requirements we make it possible for the stakeholders to participate in the requirements process. As soon as we make a requirement visible we can start testing it. and asking the stakeholders detailed questions. We can apply a variety of tests to ensure that each requirement is relevant, and that everyone has the same understanding of its meaning. We can ask the stakeholders to define the relative value of requirements. We can define a quality measure for each requirement, and we can use that quality measure to test the eventual solutions.
Testing starts at the beginning of the project, not at the end of the coding. We apply tests to assure the quality of the requirements. Then the later stages of the project can concentrate on testing for good design and good code. The advantages of this approach are that we minimise expensive rework by minimising requirements-related defects that could have been discovered, or prevented, early in the project's life.
References:
An Early Start to Testing: How to Test Requirements
Suzanne Robertson
Wednesday, February 6, 2008
Testac, a proprietary test design tool
Testac is a pioneering test design workbench that significantly enhances the quality of Maveric’s testing services and compresses test cases to a fraction of 10. Testac brings rigour to the test design phase, focussing on “What to test” and “How much to test”. It is the only knowledge-embedded test design workbench that forces a detailed systematic view of the application under test by following business processes and transaction flows to generate scenarios and cases. Moving forward, Maveric will continue to invest on this robust platform to further enrich their User Acceptance Testing (UAT) services.
“According to an IDC report on the software testing industry, the market opportunity for the Indian offshore testing companies is currently $2 billion, and is estimated to rise to $8 billion in 2008,” said Mr. Ranga Reddy, Chief Executive Officer, Maveric Systems. “Testac has led to a paradigm shift from a pure service model to an IP based services model thereby making us the only Indian company to have its proprietary intellectual property in the testing domain. The financial services domain expertise of our testing team coupled with our knowledge embedded design workbench have resulted in significant benefits to our customers,” he added.
Over the last six months, Maveric has deployed Testac for their clients in the middle-east including The Dubai Islamic Bank, Bank Muscat and Emirates Bank. Maveric has recently been awarded the coveted ‘Product Innovation Award’ by Frost & Sullivan in the software testing category at the Sixth ‘India ICT Awards’ hosted in Mumbai in Dec 2007. At present, Maveric plans to target corporates in the banking, finance, insurance and BPO sectors in India and UK.
Maveric has strongly advocated the “Model based testing” approach to effectively test end-to-end business scenarios and Testac is based on this concept. A functional framework of the related business segments is embedded into the test design workbench. Some of the key benefits of Testac include
1. Helps deliver better test coverage
2. Significant reduction in timelines upto 30%
3. Minimises test duplication
4. Carries deep domain knowledge
5. Permits prioritisation during execution
Testac Workbench has three integral components viz.,
1. A Business Modeler that holds pre-defined standard models for specific verticals. Models capture business definitions and rules at the product, transaction and business process levels.
2. A Design Generator that applies powerful algorithms and design principles to the business model to come up with optimised test cases.
3. An integrator that connects the workbench to upstream and downstream tools in defect and test management
Maveric as an organisation constantly innovates and adapts to the ever-changing landscape of testing domain. This new test design workbench will support Maveric’s commitment to provide an industry-leading software-testing platform for the future.
About Maveric Systems Ltd
Maveric Systems Ltd. is one of India’s top three independent software-testing companies since the year 2000. Over the past eight years, Maveric has been pioneering the outsourcing model in software testing. Maveric has successfully moved up the value chain in software testing by taking clients away from a resource augmentation model to provide value added IP-led services that significantly enhance quality of applications deployed by clients. As a leading pure-play, independent software testing company, Maveric today has multiple delivery locations in India, UK, Middle East and USA. Maveric’s impressive client list includes a wide array of leading software product companies, system integrators and financial institutions. With employee strength of 500, Maveric has been growing rapidly over the past five years,
For more information on Maveric Systems, please visit www.maveric-systems.com
