Disclaimer - This post is about the announcement of my pet project - http://www.iCheckWebsite.com

From past few weeks I was focusing on my pet project, iCheckWebsite.com. I was wearing many hats - product owner, scrum master, designer, occasional developer and tester. It was fun and our shiny new version is live now :-) Wearing so many hats was/is difficult and to be honest - it probably means compromising little bit. But hey, it’s okay for self funded start-ups to compromise a little bit. Iterations are not long and hopefully in every new iteration - product will become better and better.

So let me explain what is iCheckWebsite, it’s core idea and how it could be extremely useful for testers working in the web application domain.

iCheckWebsite is an on-demand test automation and content monitoring tool for websites . iCheckWebsite makes it extremely easy to test and monitor content of websites ...

Web applications are everywhere and most of us test them to earn our bread and butter. Broadly speaking, there are two types of web applications or websites - One which provide service and another which provide content. Web applications such as emails, facebook, bank or blogging platform provide a specific service and BBC, Times and many such sites provide content.

Irrespective of the type of web application, all of them need to understand user behaviour on the site and gather key usage pattern. One common way of doing this is with the help of analytic code. As a tester, it is important for us to understand how it works and how it can be tested. In this entry, I will discuss this in more detail and show you how iCheckWebsite can be used to test analytic code.

So what is Analytic code? Analytic code is usually a java script snippet which ...

Last month Komal Joshi and Patrick Martin presented @ GTAC 2008 conference in Seattle, USA. Google Test Automation Conference is one of the best conference for testing / automation and it was certainly a good experience for TestingGeek to present this at GTAC.

This presentation will give you basic information on how simple tools like SVN, batch files and task schedulers can be used to create Continuous Integration for mature desktop applications.

Solution like these are one of the best way to move teams towards more mature continuous integration environment. Using this approach, teams can start to see and appreciate benefits environment like this will bring to the projects.

Hope this presentation will be easy to follow and you will understand the basic concept behind this. Please subscribe to our newsletter if you want to remain on top of whatever is published on TestingGeek.

Rick Mugridge, Author of the famous book "Fit for Developing Software" explains the concept of story driven development, executable specifications and FitNesse. In this presentation, he addresses four main issues involved with software development and how FitNesse can be used to address following issues

1. How can we improve test coverage on a legacy system without discouraging its evolutio
2. How can QA be involved earlier and more effectively?
3. How can product managers better utilise their expertise?

Testing Mobile Handsets with FitNesse - Uffe Koch & Mark Boxall

In this lecture process and problems associated with developing mobile applications is discussed. Specifically, what kind of problems are associated with testing mobile applications, what type of test cases you need to write for mobile applications and how FitNesse can be used for mobile applications testing.

Dr Kaner talks about the requirement analysis of the Test documentation. According to Dr Kaner IEEE 829 is an paradigmatic example of standard that supports heavy weight software development process. You don't have to generate all the documents listed in 829 to be IEEE 829 compliant. Time spent in filling boiler plate information could be spent in documenting testing strategies and other useful information. The biggest problem with modern heavyweight projects is that they have a lot of inertia and resist the necessary change.

Requirements Analysis for Test Documentation (Part 2) - Cem Kaner

In this part Dr Kaner explains that using 'Prescriptive Standards' and templates will yield inappropriate products. Questioning should be used to gather documentation requirements. There are different types of stakeholders and each one is dealt differently. Dr Kaner answers some of the questions about Test Document Requirements. Needs of the organisation are more important than the ...

In this series Dr. Kaner explains what is test script and why it provide fewer benefit than it claims? It talks about the problems associated with the presence of scripts.

More Problems With Script-Based Testing

In the second part of tutorial, Dr. Kaner compares the psychology of scripted testing or procedures with the experiment he did on rats and technical support staff. He also introduces the concept of inattentional blindness because of the presence of scripts. Difference between scripted testing and checklist is also discussed in this part.

Demonstration -- Inattentional Blindness and its Implications

In this lecture Dr. Kaner demonstrate the concept of inattentional blindness by giving example. He also explains how a scripted testing practice promotes inattentional blindness. He also gives references where you can read more about inattentional blindness.

Dr. Kaner in this wonderful lecture explains the concept of specification based software testing. He explains what is specification based software testing. Importance of the specifications in the places where it is served as a contractual agreement is also discussed in this lecture. It also explains why specification might not be relevant if it served as vision document to guide the development initially and now it is not up to date. He also explains concept related to Active Reading can be applied to Specification documents.

Specification Based Software Testing - Part 2

In the second part of tutorial on specification based software testing, Dr. Kaner explains why questioning is very important in analyzing specification document. He explains different types of questions like hypothetical, behavioural, factual, historical, open/closed, context dependent and context free questions. He also gives many context free questions which can be used in any testing projects.

Specification Based ...

In this part Dr. Kaner explain how it is not possible to test completely. He demystify various concepts associated with the complete testing. He explains how 100 percent code coverage can not guarantee. Also how defect finding rate is not a good indication to infer that testing is complete. He discusses applicability of Weibull model and side effects of defect rate model. A simple example of square root is also discussed to emphasize how exhaustive testing is not possible

Impossibility of complete Testing ( Part 2 ) - Dr. Cem Kaner

In this part combination testing is discussed with three real world example to show it's importance and how it is not possible to cover all the combinations.

Bug Advocacy ( Part 1 ) - Dr. Cem Kaner

In this tutorial, Dr. Kaner explains why bug reports are important. According to him " Bug report is a tool that you use to sell the programmer on ...