Some of you might know that I have been working on my pet project TestSpicer for some time. TestSpicer has a long way to go, however I am happy to announce that it is live now.
So what is TestSpicer?
TestSpicer is a collection of RESTful web services which can be used to make test automation more efficient and effective.
Please have a look at this (around 4 minute long) video to understand TestSpicer.
TestSpicer is in beta and is free to use. It would be great if you can sign up, give it a spin and let me know what you think about it.
With TestSpicer , I hope to make randomisation mainstream - as it will take the pain out of data generation, logging, reporting and will provide invaluable insight on the data used by test automation. Right now I have focussed on data generation, but reporting, logging and visualisation ...
Last week I went to Zurich to present at Swiss Testing Days. I started my day by attending keynote - The nine forgettings - from Lee Copeland. I had attended his keynote in the past as well and he is an excellent presenter and story teller. Have a look at the slides he used and video recording . It was the same topic but it's definitely worth the time.
I agree with pretty much all the points mentioned by Lee, except certifications and boundaries.
Lee mentioned that certification is a way to grow professionally and it shows that you are serious about the profession. Well, I am not a big fan of certifications - certifications do not show that person holding certification is serious about the job. It shows that person holding certifications has passed an exam - nothing more than that. However, Lee mentioned certification as part of “Forgetting to grow” and he ...
Last week I was at San Jose for CAST 2012 to give talks on two interesting topics. My first talk was around the limitations of acceptance criteria and second talk was focused on how we can increase value of automation by introducing randomization where it make sense.
During my conversation with participants around randomization, many people suggested that I should write a blog about this - and so here it goes.
Pretty much all the test automation projects have four main elements.
- Navigation - How do you reach to the screen / page which to test
- Data - How many variations of data are possible
- Sequence - In which sequence data can be used on the page
- Operation - What are the different ways in which operations can be performed.
For example, if we take the example of registration page for any popular site such as Twitter, this is how these four elements can be used ...
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
- How can we improve test coverage on a legacy system without discouraging its evolutio
- How can QA be involved earlier and more effectively?
- 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 ...