Intro in Software QA

Intro in Software QA

What’s Software QA

Many people (especially, who is not in IT/tech industry) don’t know what QA engineer, SQA engineer, SDET, SDTE and much more abbreviation are stand for. I was super surprised when people never heard about it or don’t know what kind of profession it is. So, SQA is Software Quality Assurance  Engineer. What does it mean, just this person stands for quality of the software product? Of course NO, there are a lot more that just quality of the product/software or less bugs in the software or missing deadlines or any other issues in the software development process. Sometimes Software QA (engineer) is defined as a testing process to ensure that the quality of the product is high and software is stable and users/customers are happy and it is safe to use it. I think when QA is defined only as a testing expertise it is a wrong point.

Lets undercover what’s software QA is in real life

This will be actual in 2018 and next few (maybe 10) years. The industry of software development is still growing and there are plenty of Software QA Engineers jobs in USA and all around the world. Just check Glassdoor or LinkedIn. So, Software QA – is a process of consistent monitoring software development process or cycle and implementation procedures to achieve as high as possible standard based of the business needs.

SQA encompasses the entire software development process, which includes processes such as requirements definition, software design, coding, source code control, code reviews, software configuration management, testing, release management, and product integration. SQA is organized into goals, commitments, abilities, activities, measurements, and verifications.

So, basically, Software QA engineer is a tester, designer and project and product manager. Large amount of the developing procedures is to be loyal and democratic to the people and processes.

 

Software QA Engineer

Software QA Engineer

Of course, it is nice to have one person who can do everything like it states on the chart above, but usually it is impossible!!! This is where Software QA Engineer is joining the process. My recommendation for an experienced or future product managers or just “friendly advice” bring in your Software QA engineer as soon as your budget allow it! and you will see the difference.

Industries for Software QA

There are a lot of industries where software development won’t survive without Software QA Engineering:

  • Medical;
  • Aerospace;
  • Robotic and automotive;
  • Aviation;
  • Military;
  • Biotech;
  • Others (software development in b2b or b2c) ;

Summary

Software QA Engineer –  it is a designer,  a tester, a project manager and developer in some cases as well as “nice-to-have” some developers skills (or even linguist). There are a lot of different industries where the Engineer can find himself and build career path. Software QA Engineer is not only the last person before the release will go live, but also taking responsibilities in designing, developing, releasing and supporting the software and the business.

Dear reader, if you still have questions about what’s Software QA then do not hesitate and send us your message immediately.


Intro in software testing and software QA

Today, I have decided to start my qa/testing blog and will post all the changes that I see at my work, Software development processes, testing and releasing a new version of the software. The topic (Software QA) is massive, so, I will be telling you about my experience in my past and current projects. I don’t have a plan to write and post with any specific schedule, but I will try to make it as more frequent as possible. We are all adults and have family, kids and more-more-more :). I will start with a short introduction of myself below.

So, let’s begin. My name is Alex (Aleksei). I was born in Latvia, but lived in Belarus for almost 12 years and moved to US in 2009. For last 5+ years I work as a software QA engineer. I worked for large international and small companies in the US. I’m doing both: manual and automation testing for both web and mobile products/applications. I worked for c2c, b2c and b2b companies. I have a lot of experience in the area and, of course, found a lot bugs! WOW, can’t even remember numbers of bugs that I found. Currently, working for a small company in downtown San Diego, CA with b2b model and building my own small project here: https://my.streamfinances.com. You can read about it here: streamfinances.com The project includes web app and ios app. My LinkedIn profile:  https://www.linkedin.com/in/qatsys/ If you have any questions, you are more than welcome to ask me on LinkedIn or using our contact form on the website.


When is time to have a QA department

    When do you know it’s time to create QA department ? How big the team should be? Should you hire full-time QA testers or use Contractors?

   All these questions are coming in mind when you are ready to release Alpha/Beta or coming updates for your product/software. Let’s try to answer these questions with quick and short post today.

    When do you know it’s time to create Quality Assurance department ?
    We would say: as soon as possible. Of course, depending on the budget that you can spend on QA. Why? Because you must have the department which will work on quality of the product, have a “new look”, do regression testing before each release. You can say that developers can do this and I will answer: Yes, but developers are to develop the product, but QA is for Quality of the product, which meaning QA will help your company to grow by using product as a regular/normal user, observe user experience. It’s vital in software development. Both departments (Developers and QA) should work together to deliver high-quality product to your customers/users. Both departments should have the same goals. QA department is supposed to mitigate that risk of users losing trust in your product. So, the answer is “As soon as possible”.

    How big QA team should be? Should you hire full-time QA testers or use Contractors?
    To answer this question you must understand next: 1. Quality of your product/service is very important for the users and only users/customers are deciding if they like product or not and how buggy, overall user experience and impressions. 2. Your budget: if your budget allows you to bring a lot of experienced QA to your company – just do it. If no, hire experienced QA manager who will calculate all risks of releasing without testing as well as how many QA testers you need and strategies. There is a big myth that you must have as many QA testers as many developers you have working on your product. Other words, developers count = qa count. Bring as many QA as you can, because you want to avoid and know how your product (software, apps) works before your user starts complaining and give you low-rate review. Depending on situation and how complicated your product you can have few full-time QA and the rest hire for your need through staffing agencies or directly as a temp/part-time employees.

   In the end we would like to say: bring QA as soon as you have a chance, budget. QA could be full-time and/or temp/on-call people who will put the best effort to deliver high-quality product. Nowadays when IT industry is growing, you can find QA testers for any budget. Good luck with your product and your QA department even if you have only one temp person who is doing QA for your company.