Mikel  Okuneva

Mikel Okuneva


How to Establish a Successful Testing Process for Your Product

Testing has always been a critical factor for delivering bug-free, reliable, and secure products. With the high competition on the market and increasing customer demands the benefits testing can bring you are huge. Let’s say you have already found the right testing team. This is only a part of the solution. Now you need to organize a testing process the right way.

As a client, you may think that the testing provider defines everything about your testing project. And to some extent you are right, but that is just a part of the bigger picture. Testing is a precise process and each stage of it is extremely important as it can affect the results. The first part of the testing project — the part before the testing starts — is not an exception.

The smooth start of each testing project very much depends on the communication of the testing team and the client. To be more exact, the more information you provide, the greater the chances you will successfully carry out the tests, which will lead to a better performing product. Here are some questions to keep in mind while planning a testing project.

QTNA: The Basic List

Although much depends on the type, scale, and specific characteristics of the project, typical questions from the testing team include the following:

  1. What are your overall expectations from testing?
  2. Was the testing process performed on this project before?
  3. What are your expectations for the product?
  4. What environments are needed for testing?
  5. What tools and infrastructure should be used in the project?
  6. What test artifacts will be used during the testing process?
  7. What are the timing of the testing process and the frequency of product releases?
  8. Does your team have a testing strategy?
  9. How should the testing process be reported?
  10. How should communication between the customer and the testing team look like?

Let’s explore these questions in greater depth.

The Expectation From Testing

The first question to be answered is the question about clients’ general expectations from the testing activities. In particular, you can be asked about the circumstances and reasons which prompted you to test your product in the first place. It could be a lot of things, including the necessity to improve the quality, the reduction of the development team, or simply a desire to learn more about the product (UI/UX) for its further improvements. Once the testing team knows the goals of the testing project the options of its implementation can be considered.

Was Testing Performed Before?

The other thing that the testing team needs to know is if the testing took place before. This provides the team with understanding whether you know what testing is all about, or they should establish the testing process from scratch. If the product has been tested before the client is usually able to share some information about the process and the results achieved. This, in turn, will help the testing team to figure out which approaches are worth offering and which are not.

What Do You Expect From the Product?

Once the team knows the purpose of the testing project the next thing they will want to establish is your expectations for the product. The first important question is “Who is your target audience? In other words, you should tell the testing team about the people or the market for which your product is intended. You should also settle on the priorities of the product. What should testers be focused on — particular functions, performance, security, UI, or scalability of the product? The answer to these questions will have an impact on the testing process, in particular, on the types of tests they use.

What About the Testing Environment?

It is equally important to outline the environments on which the product will be tested. Nо wonder that you want your solution to work on all platforms, browsers, and devices to reach the biggest audience possible. But in reality, you will need too many resources to cover all the environments. At the same time, the right priorities will allow us to reduce the testing time, improve the quality of the test coverage, and detect more bugs.

Choosing the right number of environments for testing has never been easy. Luckily, there are good tools that might help. Good examples include Google Analytics and Yandex. Metrics that show on which platforms, browsers, and devices, the product is most often tested.

The question on environments is critical as testers need to know whether they have all the necessary platforms and devices to test the product. If they do, everything is fine, but if they don’t, they will have to make further efforts to configure virtual machines for the missing platforms and/or use emulators/simulators for the missing devices. It is important to discuss all the requirements of the testing environment and prepare everything in time.

Testing Tools and Infrastructure

You should also think in advance about the tools and infrastructure for the testing process. The testing tools may include:

  • Bug tracking systems (Jira, Redmine, Mantis, Trello, etc.);
  • Systems for creating test documentation, as well as for coordinating the testing process (TestRail, TestLink, etc.);
  • Supporting tools (for screenshots, removing logs, working with the database, SOUP UI for XML, etc.);
  • Automation tools (TestComplete, Selenium, etc.).

By infrastructure, we mean the testing environments, which, depending on the product scale and goals, may include:

  • Development environment;
  • System testing environment;
  • Integration environment;
  • Stress testing environment;
  • Prod-like/Pre-prod environment.

By choosing the testing tool you have to remember:

  • What tasks should be accomplished?
  • What budget for the testing tools do we have?

The answers to these questions will allow you to determine the best testing tools for your project. You should also agree with the testing team what test environments they should use and provide access to them, so they have enough time to set everything up.

Test Artifacts

Although all experienced testers know what test artifacts should be used, additional clarification never hurts. Are there any test artifacts you already use? Do you have a test plan? Are there any checklists (which ones)? Are there any written cases? Which bug report templates do you use? The answers will help the testing team to understand what test artifacts they have to create, calculate how much time it takes, and agree on the formats of the test artifacts for the testing project.

More Questions About the Product

The testing team can always ask some additional organizational questions about the product. For example: when is the scheduled release date, or how often your product will be updated, or which methodology do you use to manage your product? The information you provide to your testing team will help them plan the testing process better by spreading the testing activities by the set deadlines.

Testing Strategy

The next step is to discuss the testing strategy with your team. First, you should agree on the most critical functionality of the product, to draw their attention to it. Then the team will choose the testing method and show you what exactly will be tested and how much time it will take. The professional testing team will always explain to you the reasons for their choice and offer you several alternative options. With the right testers, you will be also informed about the consequences of waiving particular types of tests or from speeding up the testing process. This approach is the only way to create a testing strategy that will suit your business needs best.

Project Reporting

Testing helps collect various qualitative and quantitative indicators for your product (the same goes for the project) and maintain statistics. To keep it organized, you and your testing team should agree on the format of the test results. This could be a traceability matrix, graphs, or charts — anything you need. The most important thing is that this information must be visible, accessible, and understandable. As a customer, you can also request to send you daily/weekly activity reports.


Communication is a king, they say. You should be very clear about how you see the communication process with your testing team from the beginning. How often do you want to receive updates from them? Do you practice everyday meetings on your project? Are you planning to hold any training meetings for the testing team? Do you need retrospective meetings? Those are the questions that need to be answered too.

Final Thoughts

The answers to the questions described above will help you to overcome/prevent the obstacles during the testing process and contribute to the general project success. Except for catching the bugs, testing also provides you with a great amount of useful information that may help to improve the quality of the product in the future. The more well-thought-through your testing process is, the greater your chances to launch a high-quality product that works as it should and bring the best experience to the users.

#performance #testing and qa #outsourcing software development #testing environment

What is GEEK

Buddha Community

How to Establish a Successful Testing Process for Your Product
Tamia  Walter

Tamia Walter


Testing Microservices Applications

The shift towards microservices and modular applications makes testing more important and more challenging at the same time. You have to make sure that the microservices running in containers perform well and as intended, but you can no longer rely on conventional testing strategies to get the job done.

This is where new testing approaches are needed. Testing your microservices applications require the right approach, a suitable set of tools, and immense attention to details. This article will guide you through the process of testing your microservices and talk about the challenges you will have to overcome along the way. Let’s get started, shall we?

A Brave New World

Traditionally, testing a monolith application meant configuring a test environment and setting up all of the application components in a way that matched the production environment. It took time to set up the testing environment, and there were a lot of complexities around the process.

Testing also requires the application to run in full. It is not possible to test monolith apps on a per-component basis, mainly because there is usually a base code that ties everything together, and the app is designed to run as a complete app to work properly.

Microservices running in containers offer one particular advantage: universal compatibility. You don’t have to match the testing environment with the deployment architecture exactly, and you can get away with testing individual components rather than the full app in some situations.

Of course, you will have to embrace the new cloud-native approach across the pipeline. Rather than creating critical dependencies between microservices, you need to treat each one as a semi-independent module.

The only monolith or centralized portion of the application is the database, but this too is an easy challenge to overcome. As long as you have a persistent database running on your test environment, you can perform tests at any time.

Keep in mind that there are additional things to focus on when testing microservices.

  • Microservices rely on network communications to talk to each other, so network reliability and requirements must be part of the testing.
  • Automation and infrastructure elements are now added as codes, and you have to make sure that they also run properly when microservices are pushed through the pipeline
  • While containerization is universal, you still have to pay attention to specific dependencies and create a testing strategy that allows for those dependencies to be included

Test containers are the method of choice for many developers. Unlike monolith apps, which lets you use stubs and mocks for testing, microservices need to be tested in test containers. Many CI/CD pipelines actually integrate production microservices as part of the testing process.

Contract Testing as an Approach

As mentioned before, there are many ways to test microservices effectively, but the one approach that developers now use reliably is contract testing. Loosely coupled microservices can be tested in an effective and efficient way using contract testing, mainly because this testing approach focuses on contracts; in other words, it focuses on how components or microservices communicate with each other.

Syntax and semantics construct how components communicate with each other. By defining syntax and semantics in a standardized way and testing microservices based on their ability to generate the right message formats and meet behavioral expectations, you can rest assured knowing that the microservices will behave as intended when deployed.

Ways to Test Microservices

It is easy to fall into the trap of making testing microservices complicated, but there are ways to avoid this problem. Testing microservices doesn’t have to be complicated at all when you have the right strategy in place.

There are several ways to test microservices too, including:

  • Unit testing: Which allows developers to test microservices in a granular way. It doesn’t limit testing to individual microservices, but rather allows developers to take a more granular approach such as testing individual features or runtimes.
  • Integration testing: Which handles the testing of microservices in an interactive way. Microservices still need to work with each other when they are deployed, and integration testing is a key process in making sure that they do.
  • End-to-end testing: Which⁠—as the name suggests⁠—tests microservices as a complete app. This type of testing enables the testing of features, UI, communications, and other components that construct the app.

What’s important to note is the fact that these testing approaches allow for asynchronous testing. After all, asynchronous development is what makes developing microservices very appealing in the first place. By allowing for asynchronous testing, you can also make sure that components or microservices can be updated independently to one another.

#blog #microservices #testing #caylent #contract testing #end-to-end testing #hoverfly #integration testing #microservices #microservices architecture #pact #testing #unit testing #vagrant #vcr

Software Testing 101: Regression Tests, Unit Tests, Integration Tests

Automation and segregation can help you build better software
If you write automated tests and deliver them to the customer, he can make sure the software is working properly. And, at the end of the day, he paid for it.

Ok. We can segregate or separate the tests according to some criteria. For example, “white box” tests are used to measure the internal quality of the software, in addition to the expected results. They are very useful to know the percentage of lines of code executed, the cyclomatic complexity and several other software metrics. Unit tests are white box tests.

#testing #software testing #regression tests #unit tests #integration tests

Dejah  Reinger

Dejah Reinger


How to Do API Testing?

Nowadays API testing is an integral part of testing. There are a lot of tools like postman, insomnia, etc. There are many articles that ask what is API, What is API testing, but the problem is How to do API testing? What I need to validate.

Note: In this article, I am going to use postman assertions for all the examples since it is the most popular tool. But this article is not intended only for the postman tool.

Let’s directly jump to the topic.

Let’s consider you have an API endpoint example http://dzone.com/getuserDetails/{{username}} when you send the get request to that URL it returns the JSON response.

My API endpoint is http://dzone.com/getuserDetails/{{username}}

The response is in JSON format like below


  "jobTitle": "string",
  "userid": "string",
  "phoneNumber": "string",
  "password": "string",
  "email": "user@example.com",
  "firstName": "string",
  "lastName": "string",
  "userName": "string",
  "country": "string",
  "region": "string",
  "city": "string",
  "department": "string",
  "userType": 0

In the JSON we can see there are properties and associated values.

Now, For example, if we need details of the user with the username ‘ganeshhegde’ we need to send a **GET **request to **http://dzone.com/getuserDetails/ganeshhegde **


Now there are two scenarios.

1. Valid Usecase: User is available in the database and it returns user details with status code 200

2. Invalid Usecase: User is Unavailable/Invalid user in this case it returns status with code 404 with not found message.

#tutorial #performance #api #test automation #api testing #testing and qa #application programming interface #testing as a service #testing tutorial #api test

Aurelie  Block

Aurelie Block


Top 10 Automation Testing Tools: 2020 Edition

The demand for delivering quality software faster — or “Quality at Speed” — requires organizations to search for solutions in Agile, continuous integration (CI), and DevOps methodologies. Test automation is an essential part of these aspects. The latest World Quality Report 2018–2019 suggests that test automation is the biggest bottleneck to deliver “Quality at Speed,” as it is an enabler of successful Agile and DevOps adoption.

Test automation cannot be realized without good tools; as they determine how automation is performed and whether the benefits of automation can be delivered. Test automation tools is a crucial component in the DevOps toolchain. The current test automation trends have increased in applying artificial intelligence and machine learning (AI/ML) to offer advanced capabilities for test optimization, intelligent test generation, execution, and reporting. It will be worthwhile to understand which tools are best poised to take advantage of these trends.****

#automation-testing #automation-testing-tools #testing #testing-tools #selenium #open-source #test-automation #automated-testing

Mikel  Okuneva

Mikel Okuneva


Where To Learn Test Programming — July 2020 Edition

What do you do when you have lots of free time on your hands? Why not learn test programming strategies and approaches?

When you’re looking for places to learn test programming, Test Automation University has you covered. From API testing through visual validation, you can hone your skills and learn new approaches on TAU.

We introduced five new TAU courses from April through June, and each of them can help you expand your knowledge, learn a new approach, and improve your craft as a test automation engineer. They are:

These courses add to the other three courses we introduced in January through March 2020:

  • IntelliJ for Test Automation Engineers (3 hrs 41 min)
  • Cucumber with JavaScript (1 hr 22 min)
  • Python Programming (2 hrs)

Each of these courses can give you a new set of skills.

Let’s look at each in a little detail.

Mobile Automation With Appium in JavaScript

Orane Findley teaches Mobile Automation with Appium in JavaScript. Orane walks through all the basics of Appium, starting with what it is and where it runs.


“Appium is an open-source tool for automating native, web, and hybrid applications on different platforms.”

In the introduction, Orane describes the course parts:

  • Setup and Dependencies — installing Appium and setting up your first project
  • Working with elements by finding them, sending values, clicking, and submitting
  • Creating sessions, changing screen orientations, and taking screenshots
  • Timing, including TimeOuts and Implicit Waits
  • Collecting attributes and data from an element
  • Selecting and using element states
  • Reviewing everything to make it all make sense

The first chapter, broken into five parts, gets your system ready for the rest of the course. You’ll download and install a Java Developer Kit, a stable version of Node.js, Android Studio and Emulator (for a mobile device emulator), Visual Studio Code for an IDE, Appium Server, and a sample Appium Android Package Kit. If you get into trouble, you can use the Test Automation University Slack channel to get help from Orane. Each subchapter contains the links to get to the proper software. Finally, Orane has you customize your configuration for the course project.

Chapter 2 deals with elements and screen interactions for your app. You can find elements on the page, interact with those elements, and scroll the page to make other elements visible. Orane breaks the chapter into three distinct subchapters so you can become competent with each part of finding, scrolling, and interacting with the app. The quiz comes at the end of the third subchapter.

The remaining chapters each deal with specific bullets listed above: sessions and screen capture, timing, element attributes, and using element states. The final summary chapter ensures you have internalized the key takeaways from the course. Each of these chapters includes its quiz.

When you complete this course successfully, you will have both a certificate of completion and the code infrastructure available on your system to start testing mobile apps using Appium.

Selenium WebDriver With Python

Andrew Knight, who blogs as The Automation Panda, teaches the course on Selenium WebDriver with Python. As Andrew points out, Python has become a popular language for test automation. If you don’t know Python at all, he points you to Jess Ingrassellino’s great course, Python for Test Programming, also on Test Automation University.


In the first chapter, Andrew has you write your first test. Not in Python, but Gherkin. If you have never used Gherkin syntax, it helps you structure your tests in pseudocode that you can translate into any language of your choice. Andrew points out that it’s important to write your test steps before you write test code — and Gherkin makes this process straightforward.

first test case

The second chapter goes through setting up a pytest, the test framework Andrew uses. He assumes you already have Python 3.8 installed. Depending on your machine, you may need to do some work (Macs come with Python 2.7.16 installed, which is old and won’t work. Andrew also goes through the pip package manager to install pipenv. He gives you a GitHub link to his test code for the project. And, finally, he creates a test using the Gherkin codes as comments to show you how a test runs in pytest.

In the third chapter, you set up Selenium Webdriver to work with specific browsers, then create your test fixture in the pytest. Andrew reminds you to download the appropriate browser driver for the browser you want to test — for example, chromedriver to drive Chrome and geckodriver to drive Firefox. Once you use pipenv to install Selenium, you begin your test fixture. One thing to remember is to call an explicit quit for your webdriver after a test.

Chapter 4 goes through page objects, and how you abstract page object details to simplify your test structure. Chapter 5 goes through element locator structures and how to use these in Python. And, in Chapter 6, Andrew goes through some common webdriver calls and how to use them in your tests. These first six chapters cover the basics of testing with Python and Selenium.

Now that you have the basics down, the final three chapters review some advanced ideas: testing with multiple browsers, handling race conditions, and running your tests in parallel. This course gives you specific skills around Python and Selenium on top of what you can get from the Python for Test Programming course.

#tutorial #performance #testing #automation #test automation #automated testing #visual testing #visual testing best practices #testing tutorial