Despite the benefits of test automation, particularly in terms of potential cost savings, almost 40 percent of organisations are still not utilising automation in any significant capacity. This is a surprisingly high figure considering organisations’ focus on controlling project spending.
Of those who are using test automation, over 80 percent automate their functional regression testing and 64 percent use automation in test execution.
Planit Testing Index 2012: How Test Automation is Utilised
Put your training budget to good use. Develop the skills and capabilities necessary to ensure project success.
The 2012 Index reported a marginal increase in the uptake of performance testing, with 24 percent of respondents now conducting performance testing as a key part of their projects. This still indicates 76 percent of organisations put a lower priority on performance testing, including 12 percent who do not conduct any performance testing.
Planit Testing Index 2012: How Performance Testing is Conducted
Latest Whitepapers | May 15, 2013
By Teji Chopra
Senior Test Consultant
ABSTRACT: This paper attempts to dispel some common misconceptions regarding the roles of Testing and Software Quality Assurance (SQA) by referring to existing industry information and extensive professional experience. It provides insights into the differences between these terms, while also outlining challenges and providing recommendations for successful SQA teams.
The terms Testing and Software Quality Assurance (SQA) are often used almost interchangeably in the IT industry with testing professionals often classed as quality assurance professionals.
So, are these terms the same?
Although both have quality as their overall objective, a fundamental difference between the two is that testing is performed after a product has been built, or in the case of static testing, after a document has been written. In contrast, quality assurance consists of activities to ensure that quality will be built into the product.
We have previously provided an overview of project budgets and allocations as reported in the 2012 Planit Testing Index, but how do these allocations differ across project sizes and across industries?
When analysing budget allocations against average project budgets, it is possible to see a clear difference in percentage of budgets allocated to quality assurance between smaller projects (project budgets < $5 million) and larger projects (> $5 million). Specifically, smaller projects tended to spent more on development (+6%) at the expense of requirements definition (-3%) and software testing (-2%).
Planit Testing Index 2012: Project Budget Allocations by Project Size
|Small Project Budget Allocation
Project budgets < $5 million
|Large Project Budget Allocation
Project budgets > $5 million
- Software Quality Assurance: Is it the same as Testing?
- Web Services Testing
- Agile Mindset
- Working with a Distributed Team
- Traditional vs. Agile methodologies
Planit Testing Index
- Industry Stats: Test Automation Utilisation 2012
- Industry Stats: How Performance Testing Is Conducted 2012
- Industry Stats: Budget Allocations In-Depth 2012
- Industry Stats: Organisational View of Testing 2012
- Industry Stats: When Testing Starts 2012
- Planit joins Australian Banking & Financial Technology Summit as a Gold Sponsor
- UK contender Facilita enters the battle for the Australian Performance Testing Tool market
- Software Development shakes-off the GFC-blues but cannot escape trouble
- Planit brings Learntesting to Australia and New Zealand
- Failed software projects still a reality for Australian and New Zealand Organisations
- Planit Testing Index 2012 Review
- Project disasters: Are requirements really to blame?
- Leadership and not management in an Agile team
- Traditional vs. Agile methodologies
- Minority of software projects delivered problem-free