Systems outside the testing radar

When is a system small, non-complex or unprioritzed enough not to be tested? If there is a test organisation working on the bigger system that will be released to customer, what happens to the other smaller systems then? Is it so that they are almost always left untested? I usually identify these as applications that are created by one [...]

A movement called weekend testing – What it can do you and your testing career?

An extremely contiguous phenomenon is sweeping in some circles, communities of software testing; it is called Weekend testing (twitter @weekendtesting). Presumably, born out few young minds (Ajay Balamurugadas, Parimala Shankariah, Sharath Byregowda, Manoj Nair ) influenced by context driven software testing philosophy. In a short span of time it has travelled from Bangalore (the home [...]

Test This #4 – Stale Client Data

Think about your AUT. Is it possible for a user to see something on their screen that has been altered since the last time their screen refreshed? If so, you’re in luck. You can execute some stale data tests that may be fruitful. Think of an item that can be edited. Let’s call it “ItemA”. [...]

How to Start Selenium Server with Java Code

When test automating a web application using Selenium, we have to start the Selenium server first, so that a new Selenium session is created to talk to the web browser. This can be either done manually, i.e user running a command line to start the Selenium server, or to get the pure automation effect of [...]

Risks based Software Testing

What does risk mean ? Put simply, risk is something that could result in negative consequences in the future. Risk is viewed in terms of its impact and likelihood of occurrence. Risks in software testing may be broadly classified as product risks and project risks. Product risks relate directly to the software being tested, while [...]

Acceptance, buddy, paired and exploratory testing types in brief

Here’s a brief look at some of the testing types listed here Acceptance Testing black-box type tests executed by customers / their representatives small set of tests generally aligned towards real-life scenarios / use-cases purpose primarily to verify if product meets acceptance criteria and not defect detection tests can verify functional / non-functional requirements Buddy [...]

JUnit 4 Test Logging Tips using SLF4J

When writing JUnit tests developers often add log statements that can help provide information on test failures. During the initial attempt to find a failure a simple System.out.println() statement is usually the first resort of most developers.

Review: The Definitive Guide to Building Code Quality, Don Jones

This book is focused on development using Microsoft .NET and Visual Studio. For those who work with these technologies it will be easy to relate to & follow most of the content. However, the book has some general practices around software development that are useful to consider irrespective of the tools you use. The book [...]

Tag! You’re it…

Feed from Testing the future In 2008 I was attending a session for the Sogeti Test in Gouvieux. France. There I learned about standard testware. Standard testware should help companies to upgrade there outsourcing abilities for their clients. But the question was how this could be accomplished. My answer to this is by ‘tagging’. According [...]

Who’s Going to Read Your Test Plan?

Feeds from Abakas.com There are a lot of different ways to create a test plan. A test plan can be a simple list, or an excel spreadsheet, or some code, or a Word document conforming to your favorite test plan template, or the output of a test management system. All of them are legitimate, but [...]

← Previous Entries

Next Entries →