Monday, July 30, 2012

Do we have rules for story writing?


I came across this interesting article from Pixar - The 22 rules of storytelling, according to Pixar


It got me thinking - this applies to our Agile world of Software Development too! 
  • Anyone writing story cards - do you have certain rules / criteria in mind? I think quite a few things from the Pixar article apply in our world too!
  • For us Testers, do we think about the functionality in the story cards based on these rules? Or, simply put, do we think about the new functionality in the story card affects the end-product? Do we think about the big picture enough?

Monday, July 23, 2012

How will you test this?

How will you automate the testing of something like this? ... no - not the video, but the wonders they have achieved in the "Miniatur Wunderland"!


WAAT-Ruby crosses 300 downloads

I was very happy to see that WAAT-Ruby (Web Analytics Automation Testing framework) has crossed 300 downloads on rubygems.org.

Tuesday, July 17, 2012

Behavior Driven Testing (BDT) in Agile - slides uploaded

I spoke in SiliconIndia's SoftTec 2012 in Bangalore on 14th July on Behavior Driven Testing (BDT) in Agile


It was a pretty big conference - with the Test Technologies / Methodologies track having an attendance of about 250 people, and the People / Process / Business track having an attendance of about 150 people. There were good interactions with the attendees and fellow speakers during the break times.

The topic of my talk was Behavior Driven Testing (BDT) in Agile. Off late, I have been speaking on this topic at various different places in some form or the other. Click here for all information related to BDT.


Here is the abstract of this talk: 

In this talk, I will explain Agile Testing and how a technique called "Behavior Driven Testing (BDT)" can make your testing more effective. I will also cover the differences between BDD (Behavior Driven Development) and BDT, how BDT affects the Test Pyramid, and the value proposition of using BDT. 


The slides from this talk are available in the vodQA group on facebook and on SlideShare.net

Monday, July 9, 2012

vodQA Geek Night - Behavior Driven Testing (BDT) update

We hosted a vodQA Geek Night focussing on Behavior Driven Testing (BDT) at ThoughtWorks, Pune on 5th July 2012. The workshop itself was very intense and saw great participation and interactions with the attendees and the workshop facilitators.


There were many firsts for this workshop:

  • The first vodQA Geek Night
  • Event was announced, marketed and registrations done purely as a Facebook event
  • 95% attendance
Pictures and slides have been uploaded on the vodQA group in Facebook.

Contact me or the vodQA Pune team for more information / questions.

Friday, June 29, 2012

Behavior Driven Testing (BDT) in Agile

I am speaking in SoftTec 2012 in Bangalore on 14th July on Behavior Driven Testing (BDT) in Agile


Abstract: 
In this talk, I will explain Agile Testing and how a technique called "Behavior Driven Testing (BDT)" can make your testing more effective. I will also cover the differences between BDD (Behavior Driven Development) and BDT, how BDT affects the Test Pyramid, and the value proposition of using BDT. 

Feedback on WAAT

I am considering adding some functionality to WAAT. However, before I do that, I would like to know what your opinion is.


So, to all those who are either using, tried using, or, want to use WAAT: Can you please provide me some feedback based on the following questions:



  • Which flavor of WAAT do you use? 
    • Java
    • Ruby
    • Both
  • Have you faced any problems using WAAT? 
    • If yes, what problems? How did you resolve them?
  • WAAT using the httpSniffer approach has known limitations (namely: does not support https request capturing, and on non-Windows platform you need to run the tests using root access). 
    • Have you run into these limitations? 
    • How did you resolve the issue?
  • Do you find the WAAT wiki useful?
    • If not, what if done differently will provide more value?
  • Any other thoughts / comments on how WAAT can be made better?
Looking forward for your comments.

Thanks.

Anand