Category: Tips

Contract testing for API is about making sure that the API behaves according to the contract that has been agreed upon, and it can be done using different tools and frameworks.

Here’s an example of contract testing using Postman:

# Import the collection from a file
pm.test("status code is 200", function () {
    pm.response.to.have.status(200);
});
pm.test("response should be a JSON", function () {
    pm.response.to.have.header("Content-Type", "application/json");
});
pm.test("response should be not be empty", function () {
    pm.expect(pm.response.json().data).to.not.be.empty;
});

This code is a test script written in JavaScript, it check if response status is 200, if the response type is JSON and if the JSON response data is not empty. The test will fail if the API does not adhere to the contract, and the developers can use the failure message to identify and fix the issue.

Click here to learn about API Contract Testing with example using Pact framework in Python

Along with the technical skills, soft skills are equally important to grow up in the career.

Below are the most important soft skills that can help fast-track your career:

1. Time management

2. Communication

3. Organization of your work

4. Teamwork

5. Problem solving

6. Critical thinking

7. Interpersonal skills

8. Flexibility

9. Stress management

3 Steps for Determining What Test Cases to Automate

1. Know your goal and scope of the test case
2. Be objective about the test case’s complexity and risk-levels
3. Make sure that your testing efforts are well-balanced in time, efforts, and budget

The value of automated testing is proportional to the number of times a test may be repeated. Manual testing is preferable for tests that are only performed a few times. Test cases that are run frequently and require a substantial quantity of data to execute the same action are good candidates for automation.

Automating the following tasks will help you get the most out of your automated testing efforts:

• Tests that are repeated for numerous builds.
• Tests that are prone to human error.
• Tests that necessitate the use of numerous data sets.
• This is a frequently used feature that introduces high-risk situations.
• Tests that are impossible to complete by hand.
• Tests that are performed on a variety of hardware and software platforms and combinations.
• When manual testing, tests that involve a lot of time and effort.

Ultimate Productivity Toolkit – 365+ Resources to be a Super Productive Tester

A tool has been a tester’s friend from day 1. Be it a tool to remember the passwords or to make notes, a good tester has always made the best use of different tools. We have tools for many activities. A good tester not just understands the importance of tools but also knows the limitation of each tool.

Just like there are no best practices, there are no best tools. There are tools suited for each activity and the same tool might not be the appropriate one in another instance.

It is therefore very important that a tester knows at least 2-3 tools from each category.

Rahul Parwal and Ajay Balamurugadas welcome you to enjoy our collection of tools along with an inspiring quotation on each page.

Download the ebook from here: https://leanpub.com/productivitytoolkit

Written by Dmytro

No matter your app sends transactional emails or your company sends marketing ones, you must test them before reaching real users. The notion that only marketers are responsible for email testing is not quite accurate since the template debugging, email infrastructure setup and analysis of other tech email aspects are duties of dev and QA teams.

In this post, Dmytro will explain why testers need to be aware of email testing as a part of mobile testing and what elements must be fixed.

3 Email Testing Pillars to Remember:

• HTML templates need inspecting and debugging
• Ensuring email deliverability is a must
• Email infrastructure requires configuring and monitoring

Read Complete tips at: Huddle – Eurostar SoftwareTesting