QA and proud

Read the whole post on his blog.

Recently I tried http://quirktools.com/screenfly/ It is a tool to test if your site's design is responsive. You can choose among four device types: Desktop, Tablet, Mobile and TV. A nice feature is that you can rotate the device as well. I guess the user-agent is not taken into account, only if you check the "Use proxy server to mimic devices" option. Above you can see cnn.com on an LG Optimus S. Another minor flaw is that there is only one Windows model (Asus Galaxy 7) and only Safari on Desktop. 

I am proud that at Prezi we already follow this method by practicing Acceptance Test Driven Development "Walsh advis­es that teams stay ahead of the game – from spend­ing less time on doc­u­men­ta­tion, to mak­ing test­ing part of the def­i­n­i­tion of done. Teams must ensure that the story is not com­plete until test­ing is fin­ished." http://flip.it/8mqPk

There are no tests...

Testing is the process of considering what is “right”, defining methods to determine if the item under test is “right”, identifying the metrics that all us to know how “right” it is, understanding what the level of “rightness” means to the rest of the team in terms of tasks and activities, and assisting the team make good decisions based on good information to hit the level of “rightness” required.

Gojko Adzic - BDD: Busting the myths

Students playing XP lego game

Creating automated end-to-end functional acceptance tests is hard. Maintaining them over time is harder. Some agilistas even claim that the cost outweighs the benefit. In this lecture we present five principles for creating valuable, maintainable acceptance test suites. We discuss practices such as layering acceptance tests to reduce coupling between the test harness, and talk about how teams should be organized in order to efficiently manage acceptance test driven development. The core of the talk discusses how to manage the evolution of acceptance tests by organizing them as scenarios rather than as suites of story tests. Finally we show how to manage data for acceptance tests.

In this class you will learn how to debug programs systematically, how to automate the debugging process and build several automated debugging tools in Python.

Another argument Whittaker makes against defect tracking is the amount of time spent on documenting and recreating bugs that will never be fixed, stopping both testers and developers from making progress on the important code that will be released. “If you write a bug report and the bug doesn't get fixed, you have done damage. If it ain't gonna get fixed, don't report it,” he said emphatically.

SETs are SWEs who are really into testing. We help SWEs design and refactor their code so that it is more testable. We work with test engineers (TEs) to figure out how to automate difficult test cases. We also write harnesses, frameworks and tools to make test automation possible. SETs tend to have the best understanding of how everything plays together (production code, manual tests, automated tests, tools, etc.) and we have to make that information accessible to everyone on the team.