Blog

Last published posts

What is Web Performance Testing and Why do You Need It?
Posted on

Performance testing is one of the most challenging components of web application testing. Irrelevant web performance test data or wrong metrics, chosen during testing, cost companies a ton of money and effort. If done right, performance testing has all the tools needed to forecast product behavior and its response to user’s actions with an impressive…
Read more…

Load Testing vs Stress Testing
Posted on

Load testing and stress testing are both means of performance testing, so it’s not easy to draw a line of distinction between the two. However, while load testing assesses the software performance under some expected load (regular or peak), stress testing pushes the bar beyond peak conditions to determine the system’s load capacity as well…
Read more…

Volume Testing in Software Testing: Definition & Examples
Posted on

Since no testing activities, other than volume tests, check the ability of the system to process large data pools, there’s no reasonable way for teams to skip volume testing. If undetected, issues like data processing and storage issues can lead to security jeopardy or system shutdown.  It’s a volume tester’s job to ensure the software…
Read more…

The future of manual testing – a word from our partner

As many of you may be already aware, almost all new QA positions are requiring Test Automation skill set.

What doest that mean? It simply means that you must be a developer with the solid knowledge to testing frameworks.

At a minimum, this is what nowadays most leading companies are expecting from this role. Even during phone screening you will get passed on the question what is a test case or test plan and be most likely asked how to write a sort algorithm on an array without using conventional bubble or quick sort algorithms.

As agile becomes common practice in most large companies and startups, solid line between developer and QA roles becomes very blur. Developer and Tester becomes one single role. I.e., Developer opens pull request with some code for a new feature or a bug fix, and at the same time add a unit + functional test to the same pull request.

So what is going to happen to Manual Testers? Is this role dead? The answer is NOT. The manual tester will always be needed. Without human eyes it is impossible to release bug-free software! It is the fact and it is very hard to ignore! I’ve recently spoke with Zenefits, a leader in HR software for smaller firms, and their lead DevOps told me that Zenefits’ model of 0 testers on the team started failing once the company has begun to scale.

However, manual testing is already shifting towards cheaper alternative – crowd testing. Check Utest.com if you are interested. Plus due to technological break though in test automation frameworks, a number of manual testers drastically dropped from 1 tester per every 2-3 developer to 1:8 ration.

If you in a position of manual tester, what should you do? You should:

  • start learning programming;
  • start attend interviews to asses reality;
  • express initiative to pair up with Devs and start writing automated tests (API, Functional, Unit);
  • pick up easy bugs and try to fix them with devs help.

If you are confused where to start, BayQATraining is here to help you. The company conducts 100% hands-on bootcamps to address industry demand. Join bootcamps to break your fear and shift your career to next level: Schedule of courses.