As a prequel to the Let’s Test conference in May, I interviewed some of the European context-driven testers. Today we have Oliver Vilson a context-driven tester from Estonia.
Continue reading Let’s Test prequel with Oliver VilsonCategory Archives: Context-driven Testing
Let’s Test prequel with Huib Schoots
As a prequel to the Let’s Test conference in May, I interviewed some of the European context-driven testers. Today we have Huib Schoots who is a board member of the Dutch testing network association TestNet.
Continue reading Let’s Test prequel with Huib SchootsLet’s Test prequel with Jean-Paul Varwijk
As a prequel to the Let’s Test conference in May, I interviewed some of the European context-driven testers. Today we have Jean-Paul Varwijk who became a black-belt in the Miagi-Do school recently-
Continue reading Let’s Test prequel with Jean-Paul VarwijkLet’s Test prequel with Henrik Andersson
As a prequel to the Let’s Test conference in May, I interviewed some of the European context-driven testers. Today we have Henrik Andersson from the House of Test with us who also co-organized the conference.
Continue reading Let’s Test prequel with Henrik AnderssonLessons Learned from Context-driven testing
There has been some fluff and rumor around context-driven testing yesterday. Some folks even talked about the death of context-driven testing. Most of it was issued by the about page from Cem Kaner. If you haven’t read it yet, go ahead, read it now, I will wait here.
Back? Alright. Now, I would like to take a pick on what context-driven testing means to me, and why I think the whole schools concept can help us shape something. These are the rough ideas I had around a proposal for CAST 2012 which was not accepted. It is based on the combination of the schools concept with complexity thinking and the CDE-model. Oh, you don’t know that one? I will introduce it.
Here is the abstract that I submitted:
Continue reading Lessons Learned from Context-driven testingTitle: Significant Differences and Transforming Exchanges
In this workshops participants will apply three different concepts from complexity thinking to the schools of software testing model. The three different concepts – containers, differences, and transformational exchanges – will be explained in the workshop. We will directly apply complexity thinking to the schools of testing, and discuss where we see the schools help to shape different containers, what the significant differences between the schools are, and how transformational exchanges between the different schools could happen, and maybe where they will even fail.Armed with these tools, we will discuss how to evolve our craft of software testing, eventually extending the the concept of the different schools of thought, and find platforms for transforming software testing for the 21st century.
Let’s Test prequel with Zeger van Hese
As a prequel to the Let’s Test conference in May, I interviewed some of the European context-driven testers. Today we have Zeger van Hese who is – besides many other things – the program chair for this year’s EuroSTAR conference in Amsterdam.
Continue reading Let’s Test prequel with Zeger van HeseLet’s Test prequel with Johan Jonasson
As a prequel to the Let’s Test conference in May, I interviewed some of the European context-driven testers. Today we have Johan Jonasson from the House of Test with us who also co-organized the conference.
Continue reading Let’s Test prequel with Johan JonassonResponses from the programmer and tester surveys
A while ago, I called for some participation on the state of our craft. I promised back then to present some intermediate answers in late January. Here they are.
Continue reading Responses from the programmer and tester surveys8 things you ought to know if you do not know anything about hiring a software tester
In a recent blog entry over at 8thLight’s blog Angelique Martin points out to 8 things you ought to know if you do not know anything about hiring a software developer. Having been involved with the Software Craftsmanship movement since the early days, and 8thLight has played a major role in that movement early on, this list was compelling to me.
In short, Angelique reminds us to ask potential new employees for the development processes they used, their development practices, – particularly TDD, pair programming, short iterations, and continuous integration – and how they educated themselves and kept their claws sharp. She also points out that she would ask for a proof of their talent, how they estimated, how deadlines are met, and what they can say about the costs involved when developing software.
This list was so compelling to that I decided to put up a similar list with the things I was looking out for hiring a software tester. I believe there are some unique skills I would look for in a software tester that I would not necessarily look for in a programmer. So, here it is.
Continue reading 8 things you ought to know if you do not know anything about hiring a software testerTester Challenge Summary
A while ago I put up a challenge for software testers. Here is the mission I used back then:
Product:
Regression Test CalculatorMission:
Test the regression test calculator for any flaws you can find. You might gain bonus points, if you can find out how the calculation is done. Another set of bonus points if you can come up with a better approach.
In the meantime I found out that Ajay Balamurugadas actually found the link to the website, and sent it to James and Michael. I think he deserves some special kudos for this.
These are the responses I received.
Continue reading Tester Challenge Summary