Posts

Agile Testers - To Be Or Not To Be Independent?

Image
Recently I’ve been having discussions with various people on the ‘ independent software testing services ’ of a QA team/people in an organisation. Some have said there’s no way this can occur in a team using agile methodologies; others have said it’s essential to maintaining an effective and objective department devoted to improving product and process quality. My view? It depends on the definition  When it comes to asking whether a tester who is involved in a fully functioning scrum team, who is working daily with developers to define acceptance criteria (yes, I believe everyone should have a say), collaborating on test environment construction, investigating broken builds and similar complex tasks, are they 100% independent and flying the flag for the QA dept? I’d have to say no. What they’re doing, and I believe it’s what they should be doing, is working with the team to build the best possible feature in that sprint. If that’s the case, when is a tester working as a...

The Power Of The Bug Bash

Image
Question: What is the easiest and most cost effective way to implement exploratory usability testing prior to a release each sprint? Answer: A bug bash between the teams on your project. Regardless of whether your organisation has dedicated Quality assurance personnel or not, there comes a time when the people who have built a feature would like ’someone else’ to have a look at it prior to a release. Someone who will provide an objective, prejudice-free assessment of the work. This honest feedback is invaluable just before ‘flicking the switch’ and can save a lot of time and money, and prevent embarrassment. The QA/test team may have worked wonders throughout the sprint and prevented numerous issues from remaining in the final product but, along with the developers, they will have been 100% focused on the feature and are thus at a slight disadvantage when it comes to user-focused testing. They know it too well and can be prone to overlook the obvious. Although the product ...

What Is Software Testing?

What Is Software Testing?  An assessment of the conduct of the program by executing on test informational collections. Testing is executing a program with an indent of discovering Error/Fault and Failure. Contrast Between Fault, blunder and disappointment? Deficiency is a condition that makes the product neglect to play out its required capacity. Mistake alludes to contrast between Actual Output and Expected Output. Disappointment is the powerlessness of a framework or part to perform required capacity as indicated by its detail. Disappointment is an occasion; shortcoming is a condition of the product, brought about by a mistake. Read more about: Why software testing important? Software Testing Concepts  Acknowledgment testing: Formal testing led to empower a client, client, or other approved substance to decide if to acknowledge a framework or part. Specially appointed testing: Ad hoc testing did utilizing no perceived experiment plan system. Alpha test...