Quality Control – Process Street

All posts in Quality Control


15 Load Testing Tools, Tips and Methods to Protect You from Crashes

Do you find your website users complaining about it being sluggish at times? Does performance degrade when traffic is high? How certain are you that a new feature or build isn’t responsible for your laggy site? These are questions best answered through load testing.

Load testing is a branch of software performance testing. It involves subjecting a website to simulated workloads that stretch its specified operational capacity to its limits in order to assess its performance.

A slow and vulnerable site can affect your search visibility, user experience, and conversion rate — all of which can negatively impact your revenue.

In this article, I’m going to explain the advantages, goals, and metrics of load testing, and then give you 6 tools and 9 tips to try.

Continue Reading

8 Electrical Inspection Checklists to Keep Your Workspaces Safe

Electrical_Inspection_Checklist_headerAccording to the U.S. Bureau of Labor Statistics there were 32,000 dedicated electrical inspectors in the workforce in 2014.

That’s a good number of electrical inspectors and a great deal more electrical inspections!

Yet, much electrical inspection work is still being done with pen and paper, creating mountains of paperwork and making effective sharing of information difficult.

That’s why we’ve created this Process Street electrical inspection checklists process-pack.

We want to make sure the inspectors using our platform can make the most of the software to speed up their processes, record and compile information more easily, automatically generate reports, and ultimately keep making the world a safer space.
Continue Reading

FMEA: The Analysis Method to Prevent the £100m British Airways Catastrophe

fmea failure mode and effects analysis british airways catastropheBritish Airways chief executive described the incident as “catastrophic” as 800 flights were canceled and 75,000 travelers were affected.

Flight compensation website flightright.com estimated that British Airways would have to pay around €61m to passengers for refunds alone under EU legislation. Add to this the cost of reimbursing angry passengers for unexpected hotel stays and other inconveniences, and the total financial damage to British Airways has been estimated at £100m.

Why? Someone turned their data center off and on again.

The entire airline was down for almost 2 days. This wasn’t a natural disaster, it was a process failure.

In this article, we’ll explore how to spot process failures before they occur using a system called Failure Mode and Effects Analysis (FMEA). We’ll assess an overview and then delve in deeper to ground our understanding and include a premade Process Street FMEA template to help you run your own assessments in future.

This will leave us with three questions in regards to the British Airways affair:

  1. What happened?
  2. Why did it happen?
  3. How do we prevent it from happening again?

We’ll address each of these questions and look at how a company could employ FMEA in practice to tackle this kind of problem before it arises.

Continue Reading

16 Essential Steps to Writing Standard Operating Procedures

The_16_Steps_to_Writing_Standard_Operating_ProceduresWhether you’re starting a business or trying to improve an existing one, you have to understand how things are going to get done.

What tasks do you need to do? Who needs to do them? What are the best ways to approach these tasks?

Working out how these questions can be answered is the first step toward systemizing your business. The creation of processes and workflows will define the way in which your day to day activities function.

One popular approach to this is the creation of standard operating procedures. The simple definition provided by IBM for standard operating procedures is:

…a set of instructions that describes all the relevant steps and activities of a process or procedure.

Simple.

But how do we create these SOPs? What we need are standard operating procedures for creating standard operating procedures. And that’s what we’re going to give you.

We’ll look at:

  • How to create a set of standard operating procedures
  • Some advanced techniques for improving your SOPs
  • Why Process Street is a useful tool for both mapping and following your standard operating procedures

Continue Reading

Software Testing Methods: How Google and Facebook Crush Quality Assurance

google-and-facebook-testing

There’s a big difference between successful software companies and those shoddy unverified apps you get off the app store:

Quality assurance.

While small-time apps aren’t heavily used, and the creator won’t receive many complaints or bad press if anything breaks, Google and Facebook are used by billions of people worldwide.

If a bug affects 0.01% of the user base in a small app, it’s not worth the energy. If it affects 0.01% for Google and Facebook, that’s thousands of complaints, and possible media scandal to deal with. And we all know what the price of that can be.

So, when it comes to studying quality assurance there’s no better examples than two of the biggest Internet companies in the world.

I’ve deliberately not chosen to give Microsoft the time of day in this post, because I’d say their QA is pretty damn weak for their size.

…However, read on to pick up tips from Facebook and Google on how to make software that doesn’t break down, cost you more money, and cause frustration for your customers.

Continue Reading

Software Quality Assurance vs. Quality Control: What’s the Difference?

quality-assurance-vs-quality-control

Thinking the terms ‘quality control’ and ‘quality assurance’ can be used interchangeably is a common mistake.

Whoever coined those terms did nothing to clarify their differences, but in fact:

  • Quality control (QC) makes sure that your product isn’t riddled with bugs.
  • Quality assurance (QA) makes sure engineers are following processes to reduce future bugs, and write code more efficiently.

Quality control is something development teams do every day. They squash bugs in the code they wrote, and run tests to catch future errors.

Quality assurance is the overall management of development processes that make sure less testing and QC needs to be done.

At Process Street, we’ve already looked at the wider implications of QC and how to run tests on your software. We’ve even provided you with a bunch of pre-made software development processes you can adjust to your own team.

In this article, I’ll go into an explanation of quality assurance in software teams, and how you can use this information for your own developers.

Continue Reading

4 Types of Software Testing and When You Should Use Them

software-testing-types

The way customers see it, your software release cycle looks like this:

  • Take ages developing the software
  • Beta test
  • Add a few features, fix a few bugs
  • Done!

This isn’t real life. Beta testing is only one type of test your software needs to pass to avoid being a catastrophic failure.

If your software is struggling to get into a usable state, it’s probably because you’re overlooking testing.

Testing is important for two main reasons:

  1. Tests will reveal flaws in your software
  2. Tests will reveal flaws in your software development process

Note: Apart from customer-facing and QA tests, tests are code.

So, keep reading to find the types of software testing you need to make mandatory in your development team, as well as an explanation of how to do it.

Continue Reading

Get a free Process Street account
and take control of your workflows today.

No Credit Card Required