Posts Tagged ‘bugs’

The worldwide market for computer software and systems testing services is projected to reach 56 billion dollars by 2013 despite taking a hit from the global economic crisis, a report said Wednesday.
More companies are outsourcing testing services, with India establishing itself as the favourite provider, the report by industry consulting firm Ovum said.

“Both the outsourced and in-house testing services markets will grow over the next four years but not at the heady rates seen over the last four years,” it said.

“Despite this slowing, testing services will grow at a compound annual growth rate of 9.5 percent from 2008 to 2013, faster than most other (information technology) services.”

Computer software and systems are tested in-house or by specialist companies to evaluate their capabilities and find errors, including potential bugs.

Alexander Simkin, a senior Ovum analyst and author of the report, said India is catching up with European and North American testers in terms of quality while continuing to offer cheaper rates.

“Indian testing services providers used to compete purely on price through labour arbitrage. That’s changing,” Simkin said.

“They are now climbing the value chain and offering the same capability as North American and European testers.”

However, the high demand has resulted in a skills shortage in India “so we could see increasing numbers of testing services jobs going to other low-cost territories such as China, Malaysia and North Africa,” Simkin added.

By physorg.com

If cosmetic bugs are very low priority should we leave them and get focused on high priority tests or try to find them asap as they generates the first impact on customers?
Thats a stupid question but most of testers spend lot of time trying to find cosmetic bugs when they should try to find real bugs (I mean with Functional Impact)

by Sergio

Testing no es solamente ejercitar el software para detectar defectos o fallas, Testing se aplica a cada una de las etapas conocidas del desarrollo de Software

Por lo general pensamos que ejecutar pruebas es todo el testing cuando en realidad eso solo representa el 40% del testing. Porque se da tanta importancia a una sola actividad cuando los errores se pueden encontrar antes y con menor costo. Yo creo que es una cuestion de cultura el no ver mas alla de lo que creemos importante.
Testing no es solamente ejercitar el software para detectar defectos o fallas, Testing se aplica a cada una de las etapas conocidas del desarrollo de Software. Cada etapa, documento involucrado, porcion de software, planeamiento es testeable y debe ser testeado antes de ejecutar los System Tests.
Ademas involucrar los testers en etapas tempranas del desarrollo trae muchos beneficios, como ahorro del tiempo de ejecucion de tests, familiarizacion con el futuro sistema.
El ciclo elemental de Testing cuenta con las siguientes etapas:

> Planeamiento y Control
> Analisis y Disenio.
> Ejecucion e implementacion
> Evaluacion y reportes
> Actividades de cierre

Cada una de estas actividades internas al area de testing estan relacionadas con las etapas del desarrollo del software para “testearlas” y encontrar fallas antes de tener el codigo listo.
Solo dento de la etapa de ejecucion se realizan los test de:
* Component Testing (Mas conocidos como UniTests)
* Integration Testing (Mediante distintas metodologias, Bigban, Funcional, etc…)
* System Testing (Functional y No Funciona)
* User Acceptance Testing

by Sergio