{"id":7087,"date":"2023-04-27T12:32:55","date_gmt":"2023-04-27T10:32:55","guid":{"rendered":"http:\/\/blog.bart.sk\/en\/?p=7087"},"modified":"2024-01-25T13:59:46","modified_gmt":"2024-01-25T12:59:46","slug":"qa-team-tested-testcrunch-brno","status":"publish","type":"post","link":"https:\/\/blog.bart.sk\/en\/qa-team-tested-testcrunch-brno\/","title":{"rendered":"How the QA team tested TestCrunch in Brno"},"content":{"rendered":"

At the Crossuite project, testing is an important part of development. That’s why we’ve had a separate, currently 7-member testing team within it for 6 years, which is constantly improving its processes. In order to continue this trend, we decided to visit a QA conference in Brno in March. <\/b>TestCrunch<\/b><\/a> boasts the title of <\/b>“<\/span>the best and largest test conference in the Czech Republic and Slovakia<\/b>“<\/span>. As proper testers, we had to test it out. Conclusion? We agree!<\/b><\/p>\n

We’re doing it right<\/b><\/h2>\n

This is exactly what the conference confirmed. For example, in the lecture titled <\/span>“Is BDD in UI Automation Still Valid?”<\/span><\/i> Mykhailo Semenikhin<\/span><\/a> talked about the need to use <\/span>Behavior Driven Development in testing. In this case, the test scenarios are written as clearly as possible so that non-technical team members can test the software too<\/b>. For example, we write our acceptance tests in this way, so we nodded our heads happily throughout the lecture so as to say that yes, it really is great.<\/span><\/p>\n

\"\"<\/a><\/span><\/p>\n

The same was true for <\/span>Luk\u00e1\u0161 Pi\u0161ka’s<\/span><\/a> entry called <\/span>“Green Reports or How to Maintain the Tester’s Mindset”<\/span><\/i>. It talked about the fact that <\/span>when reporting to a client, it’s not uncommon to manipulate the success of reports just to make it look good<\/b>. Such an unfair technique is most common just before the date of launch of a new functionality. We, just as the speaker, don’t partake in it. <\/span>We report red tests honestly and assign priority to bugs according to their importance.\u00a0<\/b><\/p>\n

We found a bug on Alza!<\/b><\/h2>\n

My colleague, tester \u013dudo, was most interested in the presentation titled <\/span>“Your iPhone Is Not the Whole World, Test It as a Real User”. “For me personally, the best lecture was the one about web performance testing. <\/span><\/i>Radim Daniel P\u00e1nek<\/i><\/b><\/a> started by asking whether we test the applications that someone should use, in a real user environment. <\/i><\/b>It seemed like a definite answer. But then we came to the fact that<\/span><\/i> when simulating the real working environment of users, we should also account for, for example, a slow network, various<\/i><\/b> peaks<\/i><\/b> and the like. Only now did we begin to understand the principle of the question he had posed at the beginning. Usually, we test software in a test environment in our office, where the conditions are ideal. So that’s something we have to work on. But the best part of the lecture was that at the end, Radim revealed a critical bug in Alza’s production! I won’t say what it was, but it really was the cherry on the cake. :D” <\/span><\/i>In<\/span> addition to this lecture, colleagues Katka and Andrea also appreciated <\/span>“Security Testing Never Ends”<\/span><\/i> by <\/span>Mat\u011bj Groman<\/span><\/a>, because it was full of practical examples.<\/span><\/p>\n

AI as technical support<\/b><\/h2>\n

Wehat we were probably most looking forward to was the lecture called <\/span>“AI in Test Automation”<\/span><\/i> by <\/span>Rhona Asgari<\/span><\/a>. At work, we’ve already tried ChatGPT to generate automated tests, but we were mainly interested in how to use its potential to the fullest<\/span>. The presentation led us to the idea that if we teach it well and input it with relevant data, it can probably generate usable scenarios as well. On top of that, based on learning from our code, it could simply automate these scenarios.<\/b> We’re even thinking about the potential of using the chat as technical support for our customers in the future. When testing, it can learn how the application should work, and then translate this knowledge into answers to users’ questions. However, we’re still considering risks such as the topic of data leaks <\/span>committed by such a large company as Samsung<\/span><\/a>, or ignorance of the processes of intelligent chatbots’ functioning. <\/span><\/p>\n

\"\"<\/a><\/p>\n

My colleague Sam summed up the feelings from the presentation about AI nicely: <\/span>“The lecture explained the whole hype around AI today to me. Thanks to it, we subsequently tried using ChatGPT on our project as well, when writing a simple test scenario and an automated test, while entering the name of the user story and acceptance criteria. <\/span><\/i>I had a good feeling about a number of lectures that assured me that our QA standards were set correctly and we’re going in the right direction. <\/i><\/b>I was pleased with the standard of the whole conference, which was carried in a relaxed atmosphere, but at the same time it was conducted professionally. All the lecturers were very well prepared and were able to attract attention throughout the whole day of lectures.”<\/span><\/i><\/p>\n

We’re going to have a testathon!<\/b><\/h2>\n

Finally, also thanks to the lecture called <\/span>“How Testing Is Evolving in DevOps”<\/span><\/i> by <\/span>Szil\u00e1rd Sz\u00e9llo,<\/span><\/a> we’ve confirmed that <\/span>testing is an important part of the entire development spectrum, from planning up to delivery. <\/b>The QA team should make sure that its feedback reaches the creation of new functionalities as early as at the beginning of their preparation, but at the same time, of course, it must not be missing in the other steps, until the final delivery of the product. Thanks to this, it’ll be possible to detect security problems at the beginning of development, provide feedback to developers already in the process of designing prototypes and focus on the comprehensibility of the application for the target user.\u00a0<\/span><\/p>\n

\"\"
Source: https:\/\/abstracta.us\/blog\/devops\/testing-driver-devops-culture\/<\/a><\/em><\/figcaption><\/figure>\n

However, what we’d like to add to our process are stronger penetration and performance tests or AWS Fault Injection Simulator (FIS) operating on the principle of the so-called chaos engineering.<\/b> So it works with the application in random and unpredictable situations, not in logical procedures that are commonly carried out by experienced users. Alternatively, various problems are deliberately caused and how the software reacts to them is monitored. In this way, we’ll be able to identify weaknesses in the system and subsequently create programs that are able to withstand various types of malfunctions. <\/span>We’d also like to try out chaos engineering manually, for example at the bartan premiere testathon.<\/b> We believe it’ll happen soon.<\/span><\/p>\n

Conclusion in the words of our colleague Andrea: <\/span>“The lectures at the conference were a good mix, each one attracted somebody\u2019s interest. They also had great food and a variety of activities during breaks <\/span><\/i>\ud83d\ude42 <\/span>It was definitely worth the trip and we achieved the goals for which we decided to participate in the conference.”<\/span><\/i><\/p>\n

And for me personally, the conference was a great conclusion to four years of working as part of the QA team, which I have now exchanged for a DevOps position.<\/b> But I leave it in good hands and I believe that everything my colleagues learned in Brno will be put into practice. And as DevOps and QA go hand in hand, I look forward to continuing to work together, albeit perhaps on a different level. <\/span>But I still stay in the same office, with the same people around me and with the same vision \u2013 to improve the quality of the application and bring real value to end users.<\/b><\/p>\n","protected":false},"excerpt":{"rendered":"At the Crossuite project, testing is an important part of development. That’s why we’ve had a separate, currently…","protected":false},"author":30,"featured_media":7319,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","csco_display_header_overlay":false,"csco_singular_sidebar":"","csco_page_header_type":""},"categories":[210],"tags":[411,273,412,410,413],"_links":{"self":[{"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/posts\/7087"}],"collection":[{"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/users\/30"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/comments?post=7087"}],"version-history":[{"count":1,"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/posts\/7087\/revisions"}],"predecessor-version":[{"id":7089,"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/posts\/7087\/revisions\/7089"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/media\/7319"}],"wp:attachment":[{"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/media?parent=7087"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/categories?post=7087"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.bart.sk\/en\/wp-json\/wp\/v2\/tags?post=7087"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}