TMMi en Latinoamerica desde Agosto

TMMi ya posee una presencia oficial en Argentina y Latinoamérica de la mano de QAustral S.A.

HOW TO AVOID TESTERS MAKING MISTAKES OR MISSING BUGS?

Volvo S60 - 2012 Issues

Volvo denies there is a problem with our car> if so, then why a "software upgrade" .

Facebook Testing a Transaction Service Competitive to PayPal for Mobile Purchases

Will you use it?

Alguna pregunta sobre testing o ISTQB?

Si tienen alguna consulta o algo referido a examenes de testing por favor envienme sus consultas, las respondere a la brevedad.

Thursday, 28 June 2007

White Box Techniques...

Even when Black box testing techniques are cheaper and easier to perform than White-Box; white-box should be a priority while we are trying to roll out. We all know about time pressure, about testers availability and testers skills but this technique can save us from big headaches:

* It's great to validate the documentation, in some cases to create it. I've been dealing with some companies that prefer developing than documenting. If you check the structure of the application you have to able to complete all models.

* It's great to create functional tests cases from the code. It might have more impact and find more bugs. It might check some code impossible to reach with 100% functional test.

All companies thinks, when you mention White Box testing that they need a NASA engineer, it's true that not all testers know how to do this but is not more expensive that leaving bugs into the code.

Friday, 8 June 2007

Cosmetic Bugs

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)

No Testing Consequences

Ultimamente he tenido contacto con empresas que sufren las consecuencias de no testear o de no hacerlo adecuadamente. Lo cual causa terribles perdidas a nivel tecnologico y negocios.
A nivel tecnologico muchos desarrollos y hardware involucrado quedan obsoletos luego de una cancelacion de proyecto por errores no identificados a tiempo.
A nivel negocios las perdidas son importantes, cubrir costos generados de cualquier tipo puede ser una pesadilla. Resignar ganancia no es un problema, el real problema es la consecuencia: Mala imagen en el mercado.
Como concientizar a las empresas, que conocen las consecuencias, de que el testing no genera ganancia inmediata pero si a largo plazo. Cuando ocurrira esta apertura de mente para ganar nuevos mercados?


Lately, I've been in contact with companies suffering consequences about NO-Testing or wrong testing. It generates both technical and financial losses.
Talking about Tech level lot of developments and hardware stuffs got obsolete after a cancellation as a result of undiscovered bugs.
Due Business, it might become a nightmare to think about all costs generated. Isn't a big deal to resign revenue but the big problem would be your negative image now on into the market.
If all companies already know their consequences of no-testing it has no point to even try to offer this service to them . Testing needs a new mindset, a different one. It doesn't generates an immediate revenue but it will do it in long-term.
When people will try to get new markets and better business image?

I've added new links that I recommend to take a look like Morpheus Systems from London that belong to Matt Hobbs.