Skip to main content

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 other documentation is there besides functional specification?
  • Do you have a business analyst, domain expert or an end user available?
  • Are there prior functional parts in the system?
  • Are there any risk areas?
  • Which level of expertise does your team carry out?
  • Are you going to do manual or automated testing etc.? 
These points will reveal for you possible directions of testing.
As for the organisational aspect of testing consider the following tips as well:
  • Find out you team’s strong points.
  • Learn about the technical modules developed.
  • Depending of the testing type combine or decompose the modules.
  • Give every person of your team the modules consistent with their skills and knowledge.
  • Provide a constant communication between your team, developers and analysts.
  • Choose clear and analysis-free testing approaches to avoid misinterpretation.
  • Document the basics filling in the details in the process of testing if you have little time.
With these principles taken into account you may try some alternative testing approaches. To do user or acceptance testing involve an unknown user into the system so that you can detect its defects and see how users interact with it. While random testing you can test the system in your own method but this type needs basic requirements and functionality understanding. You may as well ask customers to write so called short stories on small pieces of paper that will make you separate tasks for further testing.
In conclusion, it can fairly be said that whatever the conditions of software testing, one should always think carefully and set clear goals before starting.


Popular posts from this blog

My Testbash Brighton 2017 Notes

This was my second Testbash... if you ever get the chance in the future these conferences are a must!
I took copious amounts of notes from the 9 talks and tried to highlight my key takeaways here... hope they make sense but please comment if you have any questions :-)
Amy Phillips - Continuous Delivery
A survival guide to joining a fast paced environment/project…
Where does testing fit within Continuous delivery:

As highlighted, basically from start to finish…
There are lots of things we can do when joining a project that is using Continuous Delivery but one of the main points from this talk was to do your research! There should be an element of "Continuous" in every aspect of the project.
·Learning the ling, what's the difference Continuous Delivery, Continuous Deployment, Continuous Integration, Continuous design, Continuous Improvements etc.? ·Understand what your role in the project is going to be ·Understand the teams values, What's going well and maybe what the team p…

Leeds Testing Atelier - April 2018

The Importance of Building a Good Community of Practice

Within every organisation i think we can all agree that 'collaboration' is a major factor to the success of any project or initiative.

As organisations grow, new teams are created and existing teams fragment from each other, this is natural and i doubt that will change.

So what impact does that have to an organisation?
Stress in the work place? Unmet expectations? Relationship breakdown? Low Morale? Dissatisfied Clients? Collateral damage is inevitable.
When clients are dissatisfied, they often take their business elsewhere, which costs your company money. Poor communication can lead to high employee turnover, which creates a cost of hiring and training for new positions. At the least, with lower productivity and an unclear sense of purpose, poor communication causes employers to pay for work hours that are not efficiently spent, costing money, affecting efficiency, and keeping employees from reaching their true potential.
Its sometimes difficult to work on projects where you/y…