Hypothesis Based Testing: Power + Speed. (Webinar Q&A Audio)

February 18th, 2012

We had an interactive audience for the webinar – Hypothesis Based Testing: Power + Speed. – on Feb 16, 2012. Below are a list of questions posed by the attendees to the presenter Mr T Ashok, Founder & CEO of STAG Software -

  1. How is HBT different form Risk based testing?
  2. Do I have to be a domain expert to implement HBT?
  3. What are the pre-requiste one has to have to learn HBT?
  4. In HBT it is “anticipating” the defect first and then writing the test cases accordingly i.e. focused based test case writing, but what if my “anticipation” is wrong?
  5. Do you have any tools to implement HBT?
  6. In HBT there are 9 quality levels, so do we need to do testing in all the 9 levels? L1 to L9 as you mentiond?
  7. where will we do performance testing in HBT?
  8. How do we do test design in HBT?

Listen to the answers by clicking on the play button below:

Webinar presentation
You can also access the webinar recording here.

If you have any other questions, please leave a message for us.

Hypothesis Based Testing: Power + Speed. (Webinar)

February 17th, 2012

Tools and process have been significant drivers to speed up testing. Automation is seen as a key driver to improving testing by enabling tests to done quickly and also frequently. Also adoption of lean principles via Agile models is seen as enabling focus and continuous evolution.

Our appetite for speed is yet to be satiated. So where do we go from here?

Leveraging intellect is the key to more power and speed.

STAG Software presented a webinar on Feb 16, 2012, 2.00pm to 3.00pm EST. The webinar presented a different approach to delivering “Clean Software” by enabling one to leverage his/her intellect and thereby unleash the power to generate speed.

You can view the webinar recording below:

You can hear to the Webinar Q&A audio clipping here.

You can view and download the webinar presentation slides from here.

Other related webinars:

  1. Improve defect detection with HBT
  2. HBT – a Revolutionary approach to testing software

We would love to hear from you, so leave a message for us.

Single entry, Single exit – Singular purpose JGDBDGK9RQTK

February 1st, 2012

Many times while examining existing automation scripts, it is amazing to note how much some of the automation code tries to accomplish. In a recent engagement, while examining automation code of a product with rich browser-based GUI, the automated script was found to have checks for wide range of conditions viz., data boundaries, default values of inputs, control enabling/disabling, control properties, and of course the functional behavior. One can visualize the various conditions to check and the associated long code that is rich in potentially uncovering a variety of issues. The developer of the script is proud of how much he/she has packed into the script whilst I am smiling and cringing inwardly. The “richness” is the problem.

So as a script developer, what do I have to do? Given scenarios to automate, assess the “fitness of automation” of the these. (In HBT (Hypothesis Based Testing), this is called “Fitness for Automation” with scenarios being “level-ized”. This helps in making the scenario “chewable” by the “automation”.)

Read the article written by T Ashok Founder & CEO of STAG Software (published in the Jan 2012 issue of Tea-Time with Testers, ezine) below that highlights that a scenario with a clear goal results in a “singular purpose” script and satisfies the key “single entry-single exit” criteria.

View more documents from STAG Software Pvt Ltd

We would like to hear from you, so leave us a comment.