Most Viewed Article Right Now: Will the Manual QA Role Disappears in the Next 5 Years [with Reasons]
Most Viewed Article Last Month: API Testing Terminology
Most recent article: Essential…
For example — 1.0-SNAPSHOT. This can be the next…
Well, well one of the main roles of a QA engineer from day one is to design and define test scenarios for applications they deliver. Refining and maintaining test scenarios and the test plan is a challenge that comes along the way. Let’s focus on the best way to define and design test cases to gain the best yields and reduce the maintenance overhead.
There are different practices followed in the industry when defining test cases. One such adaptation is defining each test case to be unique and independent to avoid failure due to dependencies.
Each test case should be…
However, the role will change drastically.
Please check the article on
Even though test automation is getting popular, still there are lots of companies using manual testing to deliver their products. This reveals the fact the manual QA role will not disappear in near future.
While there are lots of automation tools out there backed with AI, the tools are not matured enough or strong enough to replace a human being carrying the thinking pattern of a human.
Moreover, the product we build is used by another human being at the end of the day. Hence it should be viewed…
Let’s dig deep into different factors that will help us to determine the perfect testing method we should follow.
Manual testing is done by a human manually.
Automation testing is done with automation tools and test scripts written for the business use case.
There are pros and cons of both methods, for example, due to human errors manual testing may not be accurate. Automation testing is logical and it will not capture any shortcomings within the UI which are not affecting the execution flow.
Below are a few points that will help you to evaluate the method of testing that…
With years of experience in SDLC, the answer to the questions is a big “Yes”.
A wise man would ask how to identify un-Happy Paths in testing because we all love to see the happy path ? 😀
Simply the feature should work in the general flow as defined in the requirement document. Let’s take an example of an inventory control system.
Here, the tester will create an invoice with an existing item after login to the system, with a quantity. …
Have you ever wondered the mystery behind a QR code.
QR code has been living with us for more than two decades and it’s hardly someone has never seen a QR. Specially during the COVID-19 pandemic, QR code was able to acquire a great popularity in order to reduce contacts, peculiarly when entering a premise to record the visitor details, rather than writing with a pen, in just a matter of seconds you can mark your presence scanning the QR.
Often times when you scan the QR code, you will see a URL on your QR scanner app and expecting…
A level of testing performed combining individual components. Integration testing is used to identify faults in the interaction between unit components after the integration.
According to the test pyramid, integration tests lie on the second level and these tests will validate the interaction of the code with the external eco-system.
Comparatively slower than unit tests due to external interactions.
Let’s look at our inventory example…
I will be discussing about what is authentication, why we need authentication in APIs, what are the different authentication mechanism and the misconception of authentication vs authorization.
This is the second article in the series and if you didn’t checkout the first feel free to have a look.
In simple terms, authentication is used to identify the entity trying to access the resource. It could be a human or a machine. An ideal example from our day to day life is the finger prints you leave to open up doors in your office, Or the RFIDs tapped at each door…