Skip to main content


Showing posts from 2014

5 Tips Ensuring Effective Context Driven Testing

Great post... Thought I should share!
With so many controversies in the field of software application testing you can never be sure best testing practices will work in the context of your software or application. That’s why the need for context-driven approach to testing has arisen. And here are the 5 tips on how to smartly perform context-based, or context-driven, testing.
1. Ask Questions
What context-driven testers seem to be emphasizing the most often is the need to ask questions of everybody involved in the project. To fully grab the project’s context and get the maximum test coverage, you should ask a number of questions to stakeholders, development team, your fellow testers, etc. Asking questions can just as well be your perfect driver of career improvement beyond any specific project. By asking questions constantly and questioning the current status quo junior testers are able to learn from mentors and even the other way round. There is every evidence that successful testers are th…

3 Steps to Make Testing More Agile!

It's been a while, here is a great post I have found... More to come!
If you have a large dev team in your software testing company, you communicate closely and cooperate with other team members often, it’s time for you to acquire an agile style of the testing process. The agile development methodology is widely applied today as it gives much better results if organised properly.
Here are 3 keys to making the testing part of development projects agile and more value-driven as well.
Look outside your QA bucket
Try to get behind the QA boundaries. Take part in the analysis stage by attending meetings, helping to review user stories, etc. During such meeting sessions make a rule of giving your feedback and setting your testing expectations. Once you try to look outside your immediate QA role, you’ll understand the true purpose of both the stories and the project indeed and ensure that the features meet their purposes better. Grasping the business value of each story will let you find mor…

Step away from your PC and communicate "Face-to-Face" !

Over the past few weeks I have grown more and more amused as to how people communicate within the office. You are probably wondering why this isn’t a post related to a test type, a test method or a testing tool but more of a generic post about how we should communicate on projects. This is relevant as a post to a tester’s blog because as we all know testing fits in with the project life cycle.
Long distance communication has become key to the success of many organisations, such as the one I work for with multiple sites and not all based in the UK.
Remote workers and virtual teams are quickly becoming the norm these days, yet sending an instant message or an email is not always the answer. When you meet somebody face-to-face is when work tends to get the job done.
You are now probably wondering where I am going with this? Let me explain…
Ever sent an email regarding a bug to a team of developers? Each of those developers will probably have different ideas about a resolution, right? Emails w…

"Cannot Reproduce" Can We Get Rid Of Persistent Bugs?

Found this article on 10 steps to aid in eliminating those persistent bugs... Thought it many come in useful for some of you testers out there!

Unreproducible bugs can easily make a tester’s existence painful. Too often testers find a bug, then report it and get the answer “This is not a bug – I can’t reproduce it.” Still, the bug may be there, awaiting its next victim. Unreproducible bugs can be very much expensive because of their increased lifetime and investigation time. They may as well have a quite damaging effect on your product perception in case the users reporting such bugs are ignored. Therefore, testers should do better to prevent them. Here are 10 things testers can do to reduce the number of unreproducible bugs even now. Regularly do stress testing of the system unless you want to run across some unexpected failures when it is heavily loaded.Test timeouts. Make tests which fake or mock dependencies for timeout code testing. If the timeout code works wrong, it can cause a bug…

Ensure Effective Regression Testing in 5 Ways!

Regression testing is essential as it aims to find failures in the product after code changes, support of new environment or product release.

By regression testing you also ensure user confidence assessing if the product’s new version is better than the previous one. Although many companies still ignore its necessity and fail to run product tests after the release, this testing stage should not be overlooked. Below are 5 accepted ways to perform regression testing of your product.1. Run all existing tests
This means that all the tests written and run before should be rerun after the release. However, especially if they all are manual, testers are going to have a huge pile of work. Probably you don’t have that much time and resources to be wasted. The fact that it’s impossible to perform 100% overall testing of the product also adds to this. 2. Run tests with high risk
In this method you should take into consideration the tests presenting the most value to your business users. Mostly such t…

3 Things to a Remember While Doing Exploratory Testing!

Here is a post I found interesting... 

While doing exploratory testing it’s often difficult to decide what to start with since the opportunities abound.
In order to do it effectively we offer testers to concentrate on the three starting points to keep in mind all the way through. Don’t follow the documentation. Exploratory testing is something you can perform without any specification and scripted test cases. However, if such handy guides are at hand, it’s always tempting to resort to their instructions. This is the mindset you have to avoid. While checking in with the documentation, you tend to rely on their standpoints and assume the tactic of confirming that everything works as expected. Instead your role now is the opposite, because you have to find the points where the system fails. It’s better to do cross-reference using documentation afterwards. Without resorting to it you think broader, you may even unintentionally discover some undocumented implicit requirements, errors and incon…

What's The True Tester Mindset?

Sometimes, work can be difficult without the proper mindset. If you’re tired, angry or frustrated for instance, you’re almost guaranteed to make some careless mistakes. This is true of almost every profession. Software testing in no exception.
So what’s the proper mindset for a software tester? Much has been written on the topic – and it’s critical to your success in the field – so I figured I’d offer a few different points of view.
A professional tester approaches a product with the attitude that the product is already broken – it has defects and it is their job to discover them. They assume the product or system is inherently flawed and it is their job to ‘illuminate’ the flaws.
This approach is necessary in testing.
Designers and developers approach software with an optimism based on the assumption that the changes they make are the correct solution to a particular problem. But they are just that – assumptions.
Without being proved they are no more correct than guesses. Developers…

Risk-based Testing and Associated Challenges!

For more than two decades Risk-Based Testing (RBT) has been an effective tool in test manager’s hands, and highly acknowledged by testers and stakeholders as a key element of a software testing. Priority of RBT is to determine and identify risks so that perceived risks were classified and categorised. Thus, determining higher risks, that will be addressed in first place. Risk-Based Testing despite being a foundation of the modern international testing standards has been quite rarely applied successfully to its full capabilities due to certain challenges associated with such analysis. For majority project test managers introduction to Risk-Based Testing initially happens while they are testers. Testers primarily use RBT while system testing phase and it is a valid approach. But at the level of test manager while establishing testing strategy RBT is so much more useful and productive. Risk testing analysis, calculating and defining what particular test phases to use, addressing greater le…

Why Exploratory Testing Should Be Part Of Your Process!

Essentially testing is an exploratory task... Exploratory testing is a structured process of investigating an application by learning and understanding its use, features, and operation in a series of logically constructed but ad hoc tests.  By itself, exploratory testing can be useful, but when combined with other testing practices, it can be a powerful way to better understand the application, build more and better functional tests, and ultimately increase product quality. Exploratory testing can take many forms.  A tester might methodically execute a series of transactions as a user might do, recording the results and looking for discrepancies or inconsistencies.  Or the tester might perform a series of actions that a real user would never do, such as press the return key multiple times or type nonsensical data into a field. The goals of exploratory testing also vary.  In some cases, it serves as a final reality check on the quality of the software before determining whether or not it …

So, Different types of testing!

It is clear that software development cannot exist without testing. However not all those who need testing understand exactly what kind of testing will be appropriate. Let’s try to understand. Below are some types of testing: 1) Let’s start with Goal-driven testing. In this type of testing all tests that should be done proceed from the goals. There are actually 4 goals: Requirements-driven testing. In this type of testing, all conducted tests are designed in such way to show that all of the requirements have been tested at least one time.Structure-driven testing. Conducted tests in frames of this type of testing are aimed to detect as much bugs of software’s logical structure as possible. Structure-driven testing should not replace requirements-driven one, it should supplement it.Statistics-driven testing. Here, tests are conducted in order to convince the user that sufficient testing was applied. After this kind of testing, customers should understand if the software is ready for use or…

Software Testing and Sporting Achievement: What unites them ?

One of the most obvious spheres of human life, where you should be consistent to reach good results is sport. Ordinary people see only awards and usually don’t notice the chain of activities that have been taken to get those awards. Moreover, usually we don’t think about the people that ensure the results. The same as while talking about software product development we don’t often mention the QAs as people that ensure the quality of the software product. What stages unite the worlds of sporting achievement and software development and what is the role of QA in it? 1. ExploringActually, there should be “Step 0” – You have an idea of what you want to do and what do you want to get. But we take it by default and going to explore the subject. It is impossible to do your best in something that you didn’t learn up to the smallest details. In sport we should find out what result literally we should aim, what resources we’ll need for it, who is the best in it right now and who could aim to bec…

Testing in the dark? How to come out into the light!

Many testers get bewildered when asked to test some software without clear requirements. How not to plunge into panic and come out of this situation safely if you do not have much experience to rely on your senses – this article will tell.
Hardly ever can a tester hope for complete and accurate functional specification document. In many cases there are early deadlines, sudden customer’s requirements changes, urgent tasks, independent or temporary human resources and other obstacles that can complicate the testing process. More often there are also misunderstandings between specialists from different domains that can be prevented only by your broad competence. However here are some tips that can help even inexperienced testers.
First of all you should give yourself clear answers to some general questions: Will it be a unit or system test?Will you do functional, performance or regression testing?Is it a new product or a maintenance project?How do the developers understand the system?What o…

Why Specification by Example?

Quite a lot of the time there is, should we say healthy debate within the project team when not everybody has the same opinions. And let's admit nobody ever has the same opinions of how software will or should be developed. 
I take this from recent personal experience and really wanted to highlight my view on this technique. 
I wanted to try and clarify some misunderstandings about what project teams are trying to achieve. 
As a team we are attempting to: Create a shared understanding of the behaviour of the system to fulfil a user story by using specific, concrete worked examples to illustrate the required behaviour for a range of situationsCollaborate so that people provided their expertise and viewpoints on a story on the basis that different perspectives allow us to better consider what is required. As our Teamwork value says we are “better together than we are individually"Create these examples in a format that can be shared between, and understood by, all members of the pro…

10 Ways to boost your confidence as tester!

1. A tester should have all the materials needed to do the job and to feel comfortable at work. For these keep track of modern innovations in your domain and try to use as much helpful testing techniques as possible. In this way writing detailed scripts for tests won’t seem so long and boring. 2. Use basic test design techniques as a review for your test to further clarify some spots in specification. 3. Management’s decisions greatly affect the work of its employees, so why not provide it with your feedback more often? It will help to manage the project better and improve your working conditions. Do not feel constrained when you feel to need a longer period of time to complete the job. 4. Use statistics, try to envision the results and plan your actions accordingly. If you know that usually three fifths of tests find bugs, use this knowledge to forecast the terms of the project completion. 5. Test other people’s tests, try to find bugs, try your skills and measure your proficiency. Commu…

What features developers wish testers have?

It is believed that testers should have good relationships with developers. How much do developers differ from testers? They are often considered to be totally opposite units in the tech world, but if to take a closer look you will see that they are more alike than you have ever imagined. They have lots of similar features. You should keep in mind that it is always good to keep developer in your team. Testers and developers may be the most frightening rivals or have a mutual understanding between each other and cooperate that will bring up good benefits for testers. Because it is quite good to have an ally on your side who is as dedicated as they are. Let’s take a look to the features most appreciated by developer while cooperation with testers. The following are the traits most valued by developers: Detailed explanationDevelopers always rush to meet the deadline and often they have little time and if testers are not clear in their explanations while reporting the bugs it can lead into aw…

8 Tips for drawing testing ideas from your users!

To do a comprehensive and highly relevant testing one should constantly search for new ideas for testing. You can ask for these from analysts, developers, directors and marketers, but the most valuable share will be brought in by customers since their perception is number one for testers. So, here are 8 suggestions about how you can get guaranteed software testing ideas from users, customers and visitors. Break out the traffic reports by unique and new visitors, browser, location, entrance and exit page, keywords, referring links etc. This will give you valuable insights into the needs, wishes and behaviors of your customers. To learn about users’ motivation more accurately, ask them questions, make them fill in the text entry box, involve building in question logic and ordinal value scales. The user comments to your blog posts can reveal some significant keywords or natural phrases that you can use later in your calls-to-action and messaging. Also look for mentions about favorable featur…