For software testers to create a detailed test case during the QA process can
be tricky: sometimes it's not an option; sometimes it's wasted effort. Here
are ways to help make that decision.
Part of the skill set required to be a good tester involves the ability to
assess a software project and decide when it's worth putting in the effort to
create really detailed test cases. Sometimes the software will lend itself to
unstructured testing, sometimes the development methodology will dictate a
specific approach, and sometimes every possible facet will need to be
covered. If you plotted projects on a graph you would get a bell curve
because most of them fall somewhere in between the casual and the
How Do You Decide?
There are various factors that are going to weigh on any decision. Some of
them leave no room for ambiguity, for example:
There are legal ... (more)
Software developers and service providers need a period of usability testing
before launch to find out how the product stands up in the hands of end
users. An experienced QA team will ferret out bugs and identify major issues,
but they won't use your software like a customer will. The value of focus
testing is not up for debate, but the way you run it most definitely is.
How Does It Work?
Crowdsourcing-based usability testing services is an emerging niche and
you'll find a choice of online services capable of delivering valuable
information on your product's usability. Try My UI a... (more)
It made headlines for all the wrong reasons when it launched on October 1,
but things could have been so different for the HealthCare.gov website if
only it had been tested properly before release. Users trying to enroll
encountered all sorts of glitches, including very slow page updates, "page
not found" errors and frequent crashes.
Early server outages were blamed on an unexpectedly high volume of traffic as
nearly 5 million Americans tried to access the website on day one, but it
soon emerged that serious flaws existed in the software, and the security was
not properly assess... (more)
Traditional methods of software development went over the waterfall in a
barrel and smashed on the rocks below. The Agile Manifesto was written more
than a decade ago. Agile adoption has worked wonders for software
development. New products leap from concept to market faster than ever
Software updates are expected to roll out quickly into live products without
disruption, the cloud is growing ever larger, and mobile technology is
impacting heavily on how applications are developed. Feedback from the end
user informs the design. Documentation and planning are sidelined in... (more)
Software works the way it was designed because of a group of downtrodden,
undervalued and unsung heroes.
Often dismissively described as testers, these champions of precision can be
more accurately termed Quality Assurance. They set the bar high and work hard
to ensure that the software you buy is easy to use and efficient. Without
their expertise you would encounter a lot of inaccessible, bug-ridden
QA is frequently undervalued by software developers. It is often seen as an
unnecessary expense - a drain on time and resources. The truth is that
finding and fixing bugs... (more)