development Nov 19, 2019
blog post image

Today we want to share with you the results of the first autumn meet up. The event took place as a part of KhMobileDevs at ITOMYCH STUDIO. It was dedicated to QA-specialists. The ITOMYCH STUDIO team of QA engineers were pleased to take this initiative and did not give up the opportunity to demonstrate their knowledge and share experiences with like-minded people.
Topics for the event had been discussed for a long time and we tried to choose the most interesting one. We wanted to prepare something that would bring real practical benefit to the participants. As a result of the discussions, two topics were selected: “Usage of Test Management for Jira (TM4J) ” in the structure of testing process” and “Postman Basic Functions Required in the Testing Process and Newman Automation”.

The event brought together more than 50 participants to ITOMYCH STUDIO, which indicates that the stated topics were really interesting for the audience.

The meet up started with a report of Sergiy Kurilovich - QA-team player at ITOMYCH STUDIO. He talked about how to customize and optimize the testing processes of the banking application with the help of TM4J tool. First of all, Sergiy provided general information about the banking project “Dozens”. After that, he explained why we needed to choose a tool to manage the testing process.

Among the main selection criteria were the following options:

  • integration with Jira (to track the whole testing process);
  • test cases management;
  • tracking and managing critical bugs from a single interface;

All participants were able to see a spreadsheet of TM4J benchmarks and third-party services (such as ZEPHYR, Xray, HP-ALM / QC). What advantages made us choose TM4J?

  • a user-friendly interface;
  • separate folders for test plans and test cases;
  • versioning of test cases;
  • the ability to create bulk test cases.

Then we were able to get acquainted with the TM4J interface, see how the test cases are created and learn how to create them multiple. According to the speaker, this is very convenient when you need to create a checklist from test checks.

After that, the TM4J tool was clearly illustrated and exemplified to help build and optimize the testing processes during the work with a banking project.

Firstly, was emphasized the ability to add test cases and bugs to the tasks to Jira. It allows to visualize testing process and track the status and history of editing.

Secondly, TM4J enables QA specialists to test each other’s test cases. This need is due to the presence of the human factor in testing. Therefore, to ensure the highest quality testing, after creating the test case, the QA specialist sends it to another for approval. It is important to note that TM4J functionality displays history and also allows status to be displayed after validation.

Thirdly, TM4J allows you to create a test cycle (demonstrated in the presentation how to) - a set of test cases that must be completed in order for the feature to be fully tested. According to the speaker, every bug or feature should be closed only after it passed the test cycle.

In the finals, Sergiy shared useful links and answered all the questions that arose in the audience.

Mark Polonsky, one of the leading QA specialists in the ITOMYCH STUDIO continued the meet-up with a report on Postman.

We really love this tool and use it in every project. First of all, we received general information about this tool and learned that it is an environment that allows the API to be tested. API is an interface or communication protocol between a client and a server that is designed to simplify the construction of client’s software.

Then the Postman benefits were considered, among which are:

  • intuitive and simple interface;
  • ease of use;
  • ability easy to import the API;
  • ease of writing tests and test cases;
  • ability to export test cases;
  • integration with test cases at CI/CD pipeline;
  • wide functionality.

Postman interface was discussed, we saw how new collections could be created, how to import, run collections, where you could change the workspace, settings, view query history etc.

We got acquainted with the types of variables: global, collection, environment, data, local and found out the special aspects of their functioning.

Further, Mark provided information about the components of the standard Postman library:

  • environment (has, get, set, unset, clear);
  • globals (has, get, set, unset, clear);
  • request (url, headers.add, headers.delete, headers);
  • response (code, reason, headers, response.Time, text, json), pm.test (“Name of Test”, function).

Also drew the attention of participants to such variables as: guid, timestamp, randomInt and what they generate. Afterwards, all participants were able to take a step-by-step look at creating Postman collections and how to continue collecting them through Postman Runner. Everything was exemplified and shown in screenshots.

The report was continued with an introduction to end-to-end testing by structure:

register => verify user => exit application => enter application => edit user data => make sure changes are saved correctly.

And they also looked at such an important part as Postman Monitor, which shows collections and reports on the testing process.

After that, we got acquainted with the functionality of Newman, which, according to the speaker, is very useful, but underappreciated by the testers.

Newman exists to run collections and generate reports, its great advantage is that it runs through the Console. What are its main functions?

  • export of collections from Postman;
  • export of environment variables.

All the participants saw clearly on the screen how Postman collections are exported, Newman collections are banished, and how the reports are generated.

The speaker also noted that one of the most important functions of Newman is integration with Continuous integration, in our case, with Jenkins. The report and presentation ended with a look at the integration of Newman with Jenkins, identifying the main benefits and features of this interaction.

Overall, the event took place in a friendly discussion format and in an atmosphere of absolute QA cooperation. QA team of ITOMYCH STUDIO eagerly shared the experience and made the meet-up as useful as possible for all the participants.