Experience-based testing strategies

This article was published at EUROSTAR's Huddle as Experience-based Testing Strategies


On various software testing resources there are often mentioned some mysterious "Experience-Based Test Techniques". Teaching testing I always had a hard time trying to explain what is that. It's kind of very hard to teach "experience" :-) . One can present some practical task, designing it in a way that the students learn something, but it's impossible for them to learn exactly your experience.
In testing, we used to deal with such philosophical categories that cannot be explicitly described with a language of logic, like: Quality, Useful, Good, Good-enough, Experienced etc. (Say Hello to Plato!)

 

Test Design Techniques by learnthebasicsofsoftwaretesting.blogspot.com

Web Site UI Testing

"We were only changing the UI, so we don't need a full regression run here." - They said.

In Gerald Weinberg's "Secrets of Consulting" there was a wonderful chapter on "lullaby words". And "only" was one of them. Each time testers hear the word "only" - they start to get nervous. Or rather they smell bugs in the air :-)

I want to share my outlines that should be taken into account while testing "only UI" of a website (disregarding its platform or applied area).

Тестування UI сайту

"У нас були зміни лише на UI-ї, повністю регресію проганяти не будемо." - казали вони.

У Джеррі Вайнберга був чудовий розділ про "колиско́ві слова", і "лише" - одне з них. Щоразу як тестер чує "лише" - тестер починає нервувати. Або навпаки, радіти, бо в повітрі запахло багами :-)

Хочу поділитися своїми намітками про те, що треба брати до уваги, тестуючи "лише UI" якогось сайту (не прив’язано до платформи).