Marcelo Soares

Every tester knows that spotting critical bugs late is costly, yet testing the full user experience across systems can feel daunting. This is where process-focused testing stands out. 🧑‍💻 In this session with Tobias Müller from TestResultsIO, discover approaches that streamline testing without sacrificing coverage. If quality software is your goal, you’ll gain tools to boost efficiency and reduce maintenance by testing for the end-user journey. From 2FA to API integration, learn how to make each layer of your software run smoothly with fewer resources and less manual effort. Reserve your spot. 👇👇👇 https://lnkd.in/eAHtmiMW #digitaltesting #testautomation #automatedtesting #e2etesting #softwaretesting #customercentrictesting #customercentrictestingstrategies #TestResultsIO TestResults.io

10

1 Comment

In just a few hours, Bruno Lopes and Ole Lensmar will reveal how Testkube can transform your test automation strategy in our training session, "Turbocharge your Playwright Test Executions with Testkube." If you’re looking to overcome the limitations of traditional test orchestration, this is your chance. Experience a live demo showcasing Testkube’s capabilities in running Playwright tests and learn how to streamline your entire test execution process. Discover the benefits of adopting a cloud-native approach and get ready to elevate your testing efficiency. Join us for this insightful session to take your testing to the next level. Register now! 👇👇👇 https://lnkd.in/e6sfHPXS   #scalingtestexecution #parallelizationoftestexecution #testexecution #functionaltesting #e2etesting #loadtesting #testorchestrationplatform #Testkube #cloudnative #cloudnativeapplications #testorchestration #testingtools #automatedtestingtools #testautomation #automationtesting #softwaretesting #Playwright #Playwrightestexecution

18

1 Comment

Imagine a test orchestration platform that seamlessly integrates with your existing tools and scales effortlessly. 😎 Join us for "Turbocharge your Playwright Test Executions with Testkube," where Bruno Lopes and Ole Lensmar will demonstrate how Testkube can revolutionize your testing processes. During this training session, you'll see firsthand how Testkube's cloud-native approach addresses the limitations of traditional testing solutions. By focusing on Playwright tests, we'll show how you can streamline defining, triggering, scaling, troubleshooting, and reporting on test executions. This FREE session is designed to provide you with practical insights and tools to optimize your test automation strategy. Elevate your testing capabilities with the innovative solutions offered by Testkube. Secure your spot now! 👇👇👇 https://lnkd.in/e6sfHPXS #scalingtestexecution #parallelizationoftestexecution #testexecution #functionaltesting #e2etesting #loadtesting #testorchestrationplatform #Testkube #cloudnative #cloudnativeapplications #testorchestration #testingtools #automatedtestingtools #testautomation #automationtesting #softwaretesting #Playwright #Playwrightestexecution

25

3 Comments

Efficient and scalable test execution is a cornerstone of successful software development. 💪 In our training session, "Turbocharge your Playwright Test Executions with Testkube," Bruno Lopes and Ole Lensmar will introduce you to Testkube, a cloud-native platform designed to streamline and optimize your testing processes. Discover how Testkube can help you overcome the limitations of traditional test orchestration solutions. By focusing on the challenges of scaling and parallelizing Playwright tests, this training session will provide actionable insights and a live demo of Testkube's capabilities. Learn how to reduce manual effort, increase flexibility, and improve test coverage with this powerful tool. Enhance your test automation strategy by joining us for this informative session. Register today! 👇👇👇 https://lnkd.in/e6sfHPXS #scalingtestexecution #parallelizationoftestexecution #testexecution #functionaltesting #e2etesting #loadtesting #testorchestrationplatform #Testkube #cloudnative #cloudnativeapplications #testorchestration #testingtools #automatedtestingtools #testautomation #automationtesting #softwaretesting #Playwright #Playwrightestexecution

8

1 Comment

Dear engineers, Let's take a moment to appreciate the backbone of product quality: SDETs and QA professionals. Despite their essential role, they often face visibility challenges within companies. But why is that? And how can we change it together? 🔍 Perception Shift: It's time to recognize that SDETs and QA pros are not just support roles but experts in test automation, debugging, and more, extending beyond traditional testing. 💬 Team Collaboration: By bridging the gap between development and testing teams, SDETs and QA pros become part of decision-making and project planning, allowing synergy to thrive. 📚 Living Product Encyclopedia: With unparalleled product knowledge, SDETs are invaluable resources for architects and development teams. They possess deep insights into product architecture and design, serving as a crucial bridge between testing and development phases. ✨ Recognition Boost: Let's shine a light on their invaluable contributions. Acknowledging their diverse skills and providing growth opportunities empowers them to excel. Together, let's elevate the role of SDETs and QA. #sdets #workculture

112

1 Comment

I've spent the last couple of years really focused on understanding what distinguishes the top 1% of mid-senior QA professionals here in the US. It's a fascinating challenge because, unlike sales or development, where performance can be more easily quantified, QA is much more multifaceted. At LoopQA, we've dedicated a lot of time to refining our evaluation process. We've identified 10 key areas that consistently surface in truly exceptional QA professionals. Ultimately, these down to critical thinking/analytical ability, emotional intelligence, & ambition/will to learn. Plus a very solid understanding of terminology & methodology. It's important to note that even the best candidates typically excel in about 7 of these areas, while demonstrating competence in the remaining 3. Here's a look at the attributes we've found to be most critical: Holistic Understanding of the Product and Business: Do they connect their work to the broader business objectives? Mastery of Automation and Modern Tools: Are they capable of building and maintaining robust automation frameworks? Technical Aptitude: Do they possess a solid understanding of code, APIs, and debugging techniques? Deep Technical Proficiency: Do they actively work to prevent defects from occurring in the first place? Focus on Preventing Defects, Not Just Finding Them: Do they work closely with developers to integrate quality into the development lifecycle (e.g., pair programming, code reviews). Exceptional Exploratory Testing Skills: Are they skilled at uncovering edge cases and unexpected behavior? Advanced Problem Solving and Analytical Thinking: Do they see how different components and systems interact, understanding dependencies and failure points. Collaboration and Leadership: Do they advocate for quality and effectively collaborate with other teams? CI/CD, DevOps, and Quality Culture: Are they comfortable working within CI/CD pipelines and related tools? Strong Focus on Test Strategy and Planning: Can they develop and execute comprehensive test plans? Vision for the Future: Do they actively seek out new knowledge and adapt to evolving technologies? I'm sharing this because I think we can all learn from each other. Finding and attracting top QA talent is tough, and I believe that by discussing these core competencies, we can all get better at building strong QA teams. I'd love to hear your perspective. What qualities do you find most valuable in QA professionals? Did I miss anything? #qa #hiring #testing

137

20 Comments

Software testers juggle speed, efficiency, and quality. But what if your automation could handle complex, multi-layered processes without weighing down your team’s workflow? 🤔 In this 30-minute session with Tobias Müller from TestResultsIO, learn how to simplify testing for end-to-end digital processes. Explore methods for handling unique app requirements, managing file operations, and integrating APIs with ease. Identify critical bugs early, reduce maintenance, and let your team focus on delivering reliable features faster. See what true end-to-end automation can achieve. 👇👇👇 https://lnkd.in/eAHtmiMW #digitaltesting #testautomation #automatedtesting #e2etesting #softwaretesting #customercentrictesting #customercentrictestingstrategies #TestResultsIO

12

1 Comment

New version 1.45 - time manipulation with Clock API - ability to look for network call for single actions And many more updates and features

7

A new year begins. And my next online class is next week, in the European time zone. I'm kicking things off with my class on automation strategy for testers. This class matters because there is a lot of pressure to "automate" testing. Yet, for people who follow my philosophy of craftsmanship and professional responsibility, we must use tools in smart and responsible ways. Dishing slop is not for us. This three-day class is about how to think clearly about testing and tool use. https://lnkd.in/gq6MPeX5

97

2 Comments

If you are using Playwright Sharding and want to merge and export reports in a single way, Hasan shared with us how to do this in a very easy way. You can also find Gitlab CI/CD integration in the article. #playwright #automation #cicd #testing

18

Effective test execution is crucial for delivering high-quality software, but scaling and parallelizing these tests can be a significant hurdle. 😟 Join Bruno Lopes and Ole Lensmar in our training session "Turbocharge your Playwright Test Executions with Testkube" to discover a solution that transforms how you handle test orchestration. In this FREE session, you will learn about the innovative capabilities of Testkube, a cloud-native platform designed to support all automated testing tools. By focusing on Playwright tests, we'll demonstrate how Testkube simplifies defining, triggering, scaling, troubleshooting, and reporting on test executions. Say goodbye to costly and inflexible proprietary solutions and embrace a more efficient approach. Register now! 👇👇👇 https://lnkd.in/e6sfHPXS #scalingtestexecution #parallelizationoftestexecution #testexecution #functionaltesting #e2etesting #loadtesting #testorchestrationplatform #Testkube #cloudnative #cloudnativeapplications #testorchestration #testingtools #automatedtestingtools #testautomation #automationtesting #softwaretesting #Playwright #Playwrightestexecution

17

2 Comments

After longer than I care to mention in the world of software engineering, I am finally doing my first conference talk. https://lnkd.in/esQEA_46 #QualityEngineering #SoftwareEngineering #QE #QA #BrowserStack

90

14 Comments

With the end of Q2 coming closer, so is the end of incredibly satisfying 3 months of working together with a small group of testers to help them take their first steps in test automation. In these 3 months, in about 12 hours per week on average, we: * Selected a suitable test automation tool (Robot Framework) * Learned to build our first tests * Applied object-oriented programming principles to better structure our test (custom keywords, modules, page objects, …) * Wrote tests against SOAP, GraphQL and REST APIs as well as web UIs * Learned how to bring our tests under version control * Learned to build and maintain Jenkins pipelines as code * Added linting for our RFW tests using Robocop (which I think is so important, so yay!) In our last week, we’re automating the process of recreating our test database as part of the pipeline. Needless to say, we’ve come a long way in these three months, and I’m really happy to see the growth these testers have demonstrated and their enthusiasm for learning these new skills. All this through what’s quickly becoming a tried and tested approach for me: take small steps and build things together in your context, tech stack and infrastructure. As this project wraps up, I’m already looking forward to my next one, which is scheduled to start soon. If you think the above approach might be a good fit for your team, too, let’s talk. My schedule looks like it is opening up again from October onwards.

28

2 Comments

One common antipattern in software projects is the normalization of rush conditions, where constant urgency and tight deadlines become the norm. Teams start to treat crisis mode as a standard operating procedure, leading to burnout, poor quality work, and a culture that values speed over sustainability. Instead of addressing root causes—such as poor planning, unrealistic expectations, or technical debt—teams may adapt to rushing, which undermines productivity and innovation in the long term. Breaking this cycle and promoting balanced, sustainable work practices is important.

4

When running production smoke tests, minimising reaction time to failures is critically important. Here’s a closer look at how we monitor Cypress tests with GitLab CI pipelines and Datadog at Mister Spex. https://lnkd.in/dXksxxZ5

27

Are you in search of efficient tool for complex API mocks? Handling complex mocks in API testing can be challenging, but the Karate API tool has made it incredibly simple for us! Why Karate for Complex Mocks? 1. Ease of Use: Karate’s intuitive syntax makes defining and managing complex mocks straightforward. 2. Versatility: It supports a wide range of mock scenarios, from simple responses to intricate conditional logic. 3. Integrated Testing: With Karate, we can seamlessly integrate our mock setups into our CI/CD pipelines, ensuring consistent and reliable test environments. 4. Time Efficiency: By using Karate, we’ve significantly reduced the time needed to create and maintain complex mocks, allowing us to focus more on test coverage and quality. Using Karate for complex mocks has streamlined our testing process, ensuring our APIs are robust and reliable even in the most demanding scenarios. Have you used any other tools for complex API mocks? #APITesting #KarateAPI #DigitalTransformation #CGM

4

2 Comments

Again, this week, I observed organizations "bringing in #QA" later in the delivery flow. Why? Because there's "nothing to #test yet". I disagree; I also have an example of things to test before the first line of code is written: requirements and assumptions. #Automation #Testing #SoftwareTesting #SoftwareDelivery

30

3 Comments

AI will empower rockstar QA teams. Previously, a QA ratio of 1/5 was standardish. However, if your organization is open to AI, it's time to question why your QA team isn’t leveraging these tools. Your QA team’s output in test automation and documentation should be skyrocketing right now. If you are currently working in QA, my advice would be to get on board before you are left behind. Anyone selling “their AI” solution is likely wildly exaggerating it's ability to be hands off. They’ve likely customized an LLM and added some prompts. AI is incredible, but it's the underlying LLM that’s truly groundbreaking. A modern tester using these models can accomplish the work of three testers—if they know the right techniques. AI isn't here to take the need for testing away. It is here to make you significantly more productive. #testautomation #playwright #futureofQA #qualityassurance

80

3 Comments

What really is Virtuoso QA? Because saying it's an AI Test Automation Platform can mean anything. The great thing for me is that I personally know what it means, because I personally use it. So I can tell you. In real words. Firstly, here's what it isn't: ↣ While it is AI, it isn't autonomous ↣ It is testing, but not performance, unit, visual, penetration or accessibility ↣ It doesn't test desktop or native mobile ↣ It's not prem or installed ↣ It has GenAI, but it isn't an AI platform born only in the GenAI era ↣ It isn't hard to use. It doesn't take a long time to start. ↣ It's not code based ↣ It's not a recorder ↣ It's not open source or free So what is it then? ↣ Natural Language Programming (NLP) based. You write test steps ↣ Functional testing in the UI and API layers ↣ It is used for testing any browser based application ↣ Read: if the application is in a browser and has a DOM layer, it can be tested ↣ It is more suited to Enterprise organisations with complex needs ↣ It is more suited to data driven business applications ↣ It is AI and was born with AI back in 2017 ↣ It combines predictive and generative AI ↣ It has "true" self healing for dynamic changes, working as the test runs ↣ It is in the cloud (multiple regions) ↣ It is SaaS ↣ It is a commercial platform (based on consumption vs licenses) But even those are just lists. What Virtuoso really is to me is this: It is a means for non-technical folks (such as myself), who can still work alongside technical engineers, to be able to create working automation, quickly and efficiently. And that working automation means: data driven tests that go across multiple modules of an application or indeed multiple applications. For example - I'm not technical. Yet I can write data driven tests across Dynamics F&O (for example), doing things like create customer, create sales order, manage sales order, confirm, receive and invoice PO. Then it can also jump across into say Salesforce Commerce Cloud or D365 CE. In the same test. But more, because we use AI to heal the tests, and given browser applications are very dynamic, it means I don't need to maintain those tests. I don't even need to know that "test maintenance burden" is even a thing. So to me, "Virtuoso as an AI Test Automation Platform", what it really means is: it is an enabler for anyone responsible for testing Enterprise business applications - whether migrations, transformations, releases, patches, updates; whether system test, regression test, UAT test - they can have automation that makes their lives easier. Faster. More scalable. More quality focused. And less filled with risk. And while it is commercial, we have a stack of customers because the value returned for the investment stacks up. It provides a sound business case. I actually get a warm feeling writing about it, because I use it, and I know. It is good. In fact, it's great. Reach out for a chat if this piques your interest. Might be the best thing you did.

19

1 Comment