All posts by Wes Silverstein

Oct 15

What Are Edge Cases in Software Testing?

Software development code with a magnifying glass showing a bug

What Are Edge Cases in Software Testing?

Edge cases are a common topic of discussion in software testing. The definition of “edge case” itself is pretty straightforward. But there are many different types of bugs that can fall under the category.

Edge Case Definition and Meaning

In software testing, edge cases are bugs that are uncommon for users to encounter. Note, though, that this doesn’t always mean that it’s hard to reproduce the bug.

Sometimes the bug may be happening 100% of the time – but only on an iPhone model that makes up a very small share of the customer base. Other times, the bug might be happening across browsers/devices, but only 1% of the time.

An edge case can be a minor issue – for example, an inconsistency in the exact shade of blue used on an iOS app vs. the Android version. But it can also be a bug that’s severe when it does happen – like a crash.

Common Edge Cases

Continue reading →

Sep 20

Wes Silverstein

Automated Testing / QA Engineering

SDET vs. QA – What’s the Difference?

SDET standing next to a QA tester using a website

SDET vs. QA – What’s the Difference?

“SDET” is becoming a popular job title in many Software Engineering departments. But it’s not always clear what the difference is between an SDET vs. QA tester. Making matters more confusing, some companies use the title differently than others. Does it just mean a QA engineer or automated tester, or is there more to it? Let’s go over the basics.

What Does SDET Stand For?

SDET stands for Software Development Engineer in Test. This clarifies the fact that SDETs are involved in testing. But it still doesn’t explain exactly what they do, or how it differs from “regular” QA testers.

Differences Between SDET vs. QA

All SDETs are performing a type of QA, but not all QA testers are SDETs. Confused? You’re not alone. Sometimes it can be easier to consider what SDETs are not. In this case, we’re talking about manual testers. Continue reading →

Aug 22

Wes Silverstein

Manual Testing / QA Process

The Ultimate Guide to Regression Testing

The Ultimate Guide to Regression Testing

If you work in or with QA, you’ve likely heard the phrase “regression testing.” For most apps and websites, regression testing is done before every new release. In an Agile QA process, it’s a regular part of the QA testing vocabulary. But what is regression testing, and how do you do it?

The Definition of Regression Testing

To put it simply, regression testing means testing virtually everything in the software. Not just a new feature, and not just each general section – but every button, flow, and interaction in the app or website.

The official definition of the word “regression” is:

a return to a former or less developed state

In software, a “regression” is a bug in an area of the app or website that was previously working. Continue reading →

Jul 14

Wes Silverstein

QA Engineering

How to Start Testing the iOS 14 Beta

Three iPhone devices supported by iOS 14

How to Start Testing the iOS 14 Beta

Although iOS 14 isn’t coming out until September 2020, the iOS 14 beta is officially here! For anyone who works in QA or has an iOS app, it’s a good idea to get a head start on testing. After all, new versions of iOS can introduce bugs into previously working apps.

Ideally, Apple will be fixing any problems by the iOS 14 release date. But there’s no guarantee that your app will work perfectly when the time comes. Find out how to download and start testing the iOS 14 beta below.

iOS 14 Beta Release Date

The iOS 14 beta was released to the public on Thursday, July 9th, 2020.

The finished version of iOS 14 is expected to go live around mid-September.

How to Install the iOS 14 Beta

You can download and install the iOS 14 beta by following these steps: Continue reading →

Jun 18

Wes Silverstein

Manual Testing / QA Engineering / QA Process

How to Write Test Cases Without Requirements

When you’re testing a new feature on an app or website, it’s considered a best practice to have test cases. Ideally, the tester will be given acceptance criteria for the feature being developed. When QA knows exactly what a feature should or shouldn’t do, writing test cases can be easy enough. (If you’re feeling lost, see our article explaining test cases.) But how do you write test cases without requirements?

After all, in the real world of a fast-paced Agile process, chances are you won’t always have them. It’s pretty common to encounter a Jira ticket with a simple description, and no real list of requirements. Sure, you could ask the person responsible to add them. But it’s not always clear who that should be. (The developer? Project manager? Product manager? Higher up?)

In many scenarios, the task can get passed back and forth so long, it delays the testing process by days – if you even end up getting requirements at all. Continue reading →

May 30

Wes Silverstein

Company Culture

Tips and Tools for Working Remotely

Now more than ever, tech companies are moving towards remote work. Most who make the switch find that working remotely boosts productivity, improves worker morale, and lowers costs. One of the other major benefits? Reducing the spread of illnesses. But how do you make sure that you’re set up for success when implementing a remote workforce? Read on for our tips and tools for working remotely.

Remote Communication Tips

To make remote work successful, above all you need good communication. It may sound obvious, but there are specific tips and tools you can use to make sure you’re set for success.

1. Use the right conferencing tool for your organization.

Just because a conferencing tool is trendy doesn’t mean it’s the best fit for your particular needs. These are some of the most common tools for audio and/or video meetings: Continue reading →

Apr 28

Wes Silverstein

Manual Testing / QA Process

The Different Phases of QA Testing

The Different Phases of QA Testing

QA testing can be confusing to anyone who doesn’t work in tech – and even many who do. For those who are unaware of what QA testing entails, the vague concept might be “looking for problems in a website or app.” But there are many different phases of QA testing. Some of them happen before a product is even ready to test!

Read on to find out more about the different phases of manual QA testing.

The Design Phase

One of the first steps that QA can help with is the design phase. This might seem surprising, as QA testers aren’t exactly known for being graphic designers. But testers can provide valuable insight into user experience issues with design.

If QA can anticipate design and user interface issues before development begins, the team will save money, time, and effort. Continue reading →

Mar 31

Wes Silverstein

Automated Testing

Top 5 Test Cases to Automate

Automating Registration Test Cases (three people standing next to a mobile device with registration fields open)

Top 5 Test Cases to Automate

Automated testing has a big reputation. In fact, it’s not uncommon for teams to think their entire QA process can or should be automated. But no matter whether you have an app, website, or both, it’s unlikely that this is possible — or even a good idea. So how do you decide which test cases to automate?

Different types of software have different features and flows. In some cases, the exact same feature might even have different priorities at different companies! But there are certain core features that are common across many websites and apps. Whenever possible, these are good candidates for automation.

Even if you have the budget, staff, and resources to automate as many flows as possible, the test cases below are usually the most important to start with.

1. Registration/Signup Test Cases

Most websites and apps have the ability for users to sign up. And if your users can’t create an account, it’s unlikely that they can fully use your product. Continue reading →

Feb 28

Wes Silverstein

QA Engineering

What’s the Deal with QA Certifications?

QA Certification (certificate icon with award)

What’s the Deal with QA Certifications?

There are several major QA certifications online. What are the most popular software testing certifications, how do you achieve them, how much do they cost, and how important is it to get Agile QA certifications?

Types of QA Certifications

The two biggest sources of QA certifications are the ISTQB and the QAI. Each offers multiple types of software testing certifications.

If you’re looking to specialize in a particular type of QA (such as security testing or management), it’s worth getting the certificate specific to that position.

However, any of the more general QA certifications should be suitable for most testers. Further, if you decide to focus on a different area of QA, having a certification that only applies to your old specialty may not be useful. Continue reading →

Jan 26

Wes Silverstein

Company Culture / QA Process

How to Deal With Negative Perceptions of QA

Developer Respect for QA (person sitting at desk with computer open showing bugs and errors)

How to Deal With Negative Perceptions of QA

When you work in the field of QA testing, you’re inevitably going to encounter folks with negative perceptions of QA. While this can happen frequently, there are ways to work around it. If you can determine when to persist through the noise and when to push back, you’ll be able to accommodate whatever is thrown your way.

Developers

The overall QA and developer relationship should be collaborative. Working with a developer that respects QA can be amazing! However, the most common role that has negative perceptions of QA tends to be engineers. It’s helpful to keep in mind that this isn’t always the engineer’s fault.

Some QA testers can be condescending in their manner of reporting bugs. They might treat it as if it’s a personal critique on the developer’s self-worth. Naturally, if a developer feels that they are being personally criticized, they may react defensively. (Learn more about how to collaborate with developers in our guide to the QA and developer relationship.) Continue reading →