Here is a complete guide to testing mobile applications with our 30+ in-depth mobile app testing tutorials:
Mobile technology and smart devices are here to stay. We can all vouch for it, can’t we? It is a fact that we cannot imagine our lives without them. We use mobile devices for almost everything today – from buying groceries to watching movies. Mobile app testing has become the need of the hour. Let’s see how it is done.
This is a detailed Web Application Security Testing guide for the benefit of our readers. Let’s get started.
Due to the huge amount of data stored in web applications and an increase in the number of transactions on the web, proper Web Application Security Testing is becoming very important day-by-day.
In this tutorial, we will provide you with a detailed understanding of the meaning, tools and key terms used in Website Security Testing along with its testing approach.
Let’s begin!!
Here’s how to write a good bug report with some helpful tips and tricks. Let’s get started.
“The point of writing a problem report (bug report) is to get bugs fixed” – Cem Kaner.
If a tester is not reporting a bug correctly, then the programmer will most likely reject it stating it as irreproducible. This can hurt the tester’s morals and sometimes ego as well.
If the Bug report is effective, then its chances of getting fixed are higher. So fixing a bug depends upon how effectively you report it. Reporting a bug is nothing but a skill and in this tutorial, we will explain how to achieve this skill.
This article is about team mentoring, coaching the test team members and test team building. This article would best fit for an agile test supervisor, who wish to act as a true ‘team defender’.
Automation in Agile is very critical.
Think about the many features that are added and delivered to every Sprint. There has to be a way to make sure that the newly added feature is not impacting the existing functionality.
Due to the low Sprint duration, it is practically impossible to execute the entire suit every time the product is incremented at the Sprint ends. Having an automated test suit would definitely play a bigger role here.
However, introducing and maturing into automation would definitely take some time. Doing an initial investment in planning and designing the automation activity would definitely pay off in the long run.
Interviews play a major role in the life of any human. Mostly all of us aim to clear the interviews on the first attempt.
In this tutorial, you will learn some tricky manual testing questions and answers, along with examples to help you crack the interview easily.
These interview questions will be very useful for beginner, intermediate, and experienced testers. These questions are quite tricky, hence you need to answer them carefully.
Let’s move on!!
This article is an extensive Continuous Integration Process Tutorial for the benefit of our readers.
In our previous tutorial, we have explained how Shift left testing in detail.
Earlier, we understood the nuances of Continuous Delivery (CD) where we have production-ready software at any point via continuous feedback loops. Continuous integration (CI) is the real meat behind the CD process and is the reason that makes Continuous Delivery possible.
To understand CI, let’s take the terms at face value and deduce a basic definition. The first word means “ongoing” or “frequent” and the second “merged” or “made part of”. So CI is a process where something is being “merged”-“frequently”.
Logically the next question is: What is something being merged and where is it merged?
Considering that the CD is just the conceptual extension of CI, the answer is sort of obvious, isn’t it?
The “something” that is being merged is code and the “where” is a repository or Version control.
Thus, continuous integration is a process where the code is checked into a repository very frequently.
Additionally, as discussed in the previous article, tests are run immediately to catch any errors each time a code check-in happens thereby setting up the necessary feedback loop for a Continuous Delivery.
Suggested Reading => Excellent DevOps Training Tutorials
In this article, we will learn about the Planning Poker Technique also called Scrum Poker Cards. It is an agile estimation process and planning technique, which is very popular, easy, and simple.
The art of estimation is known to all. We estimate every day in our lives. Most of us can estimate the weight of the vegetables just by holding them and even gauge the ripeness of a fruit by its aroma.
In this article, we have explained the role of Business Analysts in SCRUM and why QA is the best for this role. Let’s get started.
A Business Analyst who is briefly referred to as a BA plays a very important role in SCRUM. This person is the link between the product owner/customer and the technical IT team.
Though we have come across several tutorials on our website on BA, we assure you that this tutorial will be unique and explain to you the importance of BA in SCRUM.
Let’s Begin!