Archive | Testing Methodologies

Explore Capabilities, Not Features

Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko is the co-author of a book called 50 Quick Ideas to Improve Your Tests.

As software features are implemented, and user stories become ready for exploratory testing, it’s only logical to base ipad-820272_1280exploratory testing sessions on new stories or changed features. Although it might sound counter-intuitive, story-oriented exploratory testing sessions lead to tunnel vision and prevent teams from getting the most out of their effort.

Stories and features are a solid starting point for coming up with good deterministic checks. However, they aren’t so good for exploratory testing. When exploratory testing is focused on a feature, or a set of changes delivered by a user story, people end up evaluating whether the feature works, and rarely stray off the path. In a sense, teams end up proving what they expect to see. However, exploratory testing is most powerful when it deals with the unexpected and the unknown. For this, we need to allow tangential observations and insights, and design new tests around unexpected discoveries. To achieve this, exploratory testing can’t be focused purely on features. Continue Reading →

Continue Reading

Software Projects Suffer From Poor Oversight Methodology

A large software project funded by the British government recently experienced massive setbacks partially due to an Software Methodologyill-suited development methodology.

Perhaps more so than any other industry, the IT sector has repeatedly found itself subject to business leaders looking to implement the latest hyped trends without properly considering how these implementations will fit into the existing operational structure. As soon as new technological advancements are released to the business market, C-level officers scramble to be one of the first to have it integrated into their enterprise.

Even departments with deeply complex workloads and daily responsibilities such as quality assurance teams are not immune to external interference. They may be pressured to employ the latest craze even when that solution does not completely meet their operational needs. Continue Reading →

Continue Reading

Defining Your Role as a Tester

Recently, I have found myself focusing less on the quality of an organization’s products from amarkusgaertner tester’s perspective. At this point, I find myself more and more in the role of helping organizations see the larger picture: How are they set up? What causes conflicts? How does the structure of the organization help build better quality? Most recently, I came across the work from Frederic Laloux and his book titled “Reinventing Organizations“.

Laloux has observed several companies in various fields that have a different structure than more traditional companies. The fields he examines range from nursing to car parts manufacturing. One of the things Laloux found out while studying these companies was the practice of self-defined roles. The idea is this: As an employer, you find out where you passion lies, and what you are good at doing. Additionally, you find out how your skills and your passions can bring value to your team, and your company. Then you go out, take advice from your peers, in order to define the role that you want to fill.

Ever since I read this, I wondered whether a different definition for testers based on this practice might be useful, and where it might harm larger efforts. Let’s explore these ideas. Continue Reading →

Continue Reading

Auditing and Software Testing: What’s the Connection?

The following is a guest submission to the uTest Blog from Sanjay Zalavadia of Zephyr.clipboard

Proper software testing and quality assurance requires more than just versatile, reliable tools. Stakeholders must also ensure that team members are interacting well, making relevant contributions and working toward predefined testing metrics.

How software auditing and testing complement each other

Fortunately, there’s a lot of overlap between having a sound technical solution and a good software audit process. The two essentially have a complementary relationship:

Continue Reading →

Continue Reading

Q&A: ‘Let’s Test’ Leader Talks Global Reach of Context-Driven Testing, Previews Conference

Johan Jonasson is one of the organizers of Let’s Test conferences, which celebrate the context-driven school of JohanJonassonthought. In addition to co-founding testing consulting firm House of Test, Johlets-test-logo-180x47pxan is a contributing delegate at the SWET peer conferences, and has spoke at several national & international software testing conferences. He is also an active member of the Association for Software Testing (AST). Follow him on Twitter @johanjonasson.

Let’s Test 2015 is slated for May 25-27, 2015, in Stockholm, Sweden, and uTest has secured an exclusive 10% discount off new registrations. Email testers@utest.com for this special discount code, available only to registered uTest members.

In this interview, we talk with Johan on the global, inclusive context-driven testing community, and get a sense of what testers can expect at the 2015 edition of Let’s Test.

Continue Reading →

Continue Reading

ISO 29119: Why is the Debate One-Sided?

unnamedIn August, the Stop 29119 campaign and petition kicked off at CAST 2014 in New York. In September, I wrote on the uTest Blog about why the new ISO/IEC/IEEE 29119 software testing standards are dangerous to the software testing community and good testing.

I was amazed at the commotion ‘Stop 29119’ caused. It was the biggest talking point in testing in 2014. Over six months have passed, and it’s time to look back. What has actually happened?

The remarkable answer is – very little. The Stop 29119 campaigners haven’t given up. There have been a steady stream of blogs and articles. However, there has been no real debate; the discussion has been almost entirely one-sided.

Continue Reading →

Continue Reading

When You Should Choose Manual vs. Automated Testing

ibook-software-developmentThe following is a guest post to the uTest Blog by Eli Lopian of Typemock.

QA analysts and IT firms are often confronted with the same question when testing a software project — whether to go with manual software testing options or to try out new automated techniques.

In certain situations, there are clear advantages to working with automated software testing solutions, and other times the automated software technology is too leading-edge and could wind up costing you way more than it’s worth. That’s why it’s essential to weigh the costs and benefits according to each project.

Manual Software Testing 

Manual Software Testing is the process of going in and running each individual program or series of tasks and comparing the results to the expectations, in order to find the defects in the program. Essentially, manual testing is using the program as the user would under all possible scenarios, and making sure all of the features act appropriately.

Continue Reading →

Continue Reading

Is Scripted Testing Just for the Newbie Tester?

Scripted testing naturally seems like it’s a match made in heaven just for the novice tester.Microsoft Web Test Managment Runner Hub Test Runner Anna Russo

After all, you have steps and directions clearly defined — wouldn’t the inviting structure to the scripted testing compensate for a lack of experience on the part of the tester? Not necessarily, if you ask our uTesters, whom recently approached the topic in a lively Analyze This testing debate in our uTest Forums.

Most of our community members found that while experienced testers may be spending their time creating test cases and junior testers executing them, there were several notable reasons as to why executing these important steps can’t just be left exclusively to the novice.

Continue Reading →

Continue Reading

Authors in Testing Q&A With Agile Testing Champion Lisa Crispin

Lisa Crispin was voted the Most Influential Agile Testing Professional Person at Agile Testing Days 2012 by her peers, and enjoys working asCrispinDonkey a tester with an awesome agile team. She shares her experiences via writing, presenting, teaching and participating in agile testing communities around the world.

She is also the author and contributor of numerous software testing books, including her latest, released in October and co-authored with Janet Gregory, More Agile Testing: Learning Journeys for the Whole Team. You can learn more about Lisa’s work on her site, and follow her on Twitter @lisacrispin.

In this uTest interview, Lisa explains the reality of agile adoption and suggests ways teams can succeed with agile.

uTest: Where have companies or teams gone most wrong when rolling out agile in their organizations?

Lisa Crispin: Many organizations don’t understand that to succeed at software development, we have to focus on delivering the best possible quality, rather than focusing on speed. Too many think that “agile” means “fast.” You need a big investment in time and training so that teams learn important practices such as TDD, CI, specification by example/behavior-driven development, helping business stakeholders identify the most valuable features, and so on. Teams that don’t nurture a learning culture where failure is tolerated, experiments are supported, and the team has diversity, accumulate too much technical debt and fail.

Continue Reading →

Continue Reading

What is Exploratory Testing? Find Out with a New Course and Webinar

Exploratory testing (ET) is a hot topic within the testing world. Testers who are not familiar with exploratory testing are looking for resources to understand what it is and how to get started testing in this way. binocular_man-300x273

We recently debuted a new course in uTest University called “What is Exploratory Testing?” penned by Lucas Dargis and Allyson Burk. In it, we look at the “traditional” approach to testing, and review what ET is and how it differs from scripted testing.

We also look at why you should use exploratory testing and wrap up by showing testers how to get started. In the course excerpt below, we answer the question: what is exploratory testing?
Continue Reading →

Continue Reading

How Sesame Street Can Help You Become a Better Software Tester

indexAll I really need to know, I learned in Kindergarten.

STARWEST presenter Robert Sabourin – a 30+ year veteran and well-respected member of the software development community – took that nugget of conventional wisdom and put his own unique tech spin on it in his course on Testing Lessons Learned from Sesame Street.

While the topic was fun and lighthearted, Rob took his subject matter seriously and impressed on attendees just how important it is to learn and master the basics. But what are “the basics”?

Let’s take a closer look at what you really need to know to build a solid software testing foundation.

Rob’s presentation focused on two main areas of professional – and personal! – development: cognitive skills and social skills. Developing your cognitive skills allows you to think more analytically, to develop efficient models and lay out precise explanations for your processes and reasoning. Strong social skills elevate your ability to collaborate to a whole new level of effectiveness and can help grow your reputation as a thought-leader.

Continue Reading →

Continue Reading

How We Really Need to Stop ISO 29119

After some real consideration, I have decided to sign the Stop 29119 petition, and along the way also signed the Professional Tester’s Manifesto.stop-29119

The main reason that really resonates with me is that companies, who would normally not use the standard, would be compelled to comply with it just to win business. If there are even a few companies that conform to the standard which are successful, and it doesn’t have to be because they comply with the standard, others will try to follow their path.

At some point, almost every company complies with the standard, and no one knows the reason, only just that the paperwork is unbearable, there isn’t any room for actual testing, and they are afraid to step out of this vicious circle. I do not wish for the testing field to go through this, and that is why I have signed the petition.

But here is where it gets tricky: I think the people who started this opposition to stop the ISO should have thought more about their actions before jumping the gun. One of the few problems I have with this course of opposition is that it gives too much power to the body behind the standard. After some time, all this opposition will turn into just information. People searching for testing-related information may come across all these countless blogs against 29119, and the only thing they will do is research the standard and tell themselves that so many people wrote about it, they should try it, and maybe convince their companies to comply with it.

Even negative advertising is still advertising — it is always of some value to the product being advertised — and gives it some kind of power in the form of public awareness. The proof can be, for example, the ISTQB. As a new tester few years ago, I wanted to get certified (I didn’t) because everybody was talking about it. It was not in a good light, but I still thought it would help me land a good job. There weren’t any other options, so what should a new tester do in this case?

Continue Reading →

Continue Reading