Luigi Olibano

🦸 I’m building a tool that makes QA testers look like superheroes. Too often, testers are stuck doing repetitive work that doesn’t show the real value they bring. That ends now. I’ve been building QA Copilot, an AI-powered assistant designed to: ⚡ Instantly generate clean, professional test scripts from user stories ⚡ Adapt to your workflow with multiple output styles (step/expected, tables, JSON, narrative) ⚡ Switch modes between Feature Tests, Regression Tests, and Smoke Tests ⚡ Support testers in story sizing discussions with QA-focused reasoning (test effort, risks, regression impact) The idea is simple: stop wasting time on boilerplate, and start showing your expertise in coverage, risk, and testability. For contractors and QA pros, it’s the kind of tool that makes you stand out - faster delivery, sharper conversations, and more confidence in your process. Early access is open. Join the whitelist here for Free access in the very near future: 👉 https://lnkd.in/e2PA_AtH

608

53 commenti

In my first automation interview, I failed not because I didn’t know Selenium but because I couldn’t explain it simply. That’s when I realized: Interviewers don’t want buzzwords. They want clarity. So I put together a no-fluff document with the 10 automation questions that appear in every QA round explained with real-life examples: ✔ Selenium = Robot that clicks on websites ✔ POM = Fix one file, not 50 scripts ✔ API Testing = Did Swiggy send back “pizza” restaurants or not? ✔ Continuous Testing = No human clicks “Run Tests” anymore If you’re a fresher: stop memorizing definitions. Practice with demo sites (DemoQA, SauceDemo, OrangeHRM) + daily apps (Amazon, Swiggy, Flipkart). 📄 Grab the document, read it out loud, and you’ll be ready to face automation interviews with confidence. #QATesting #TestAutomation #Selenium #API #QAInterviewPrep #CareerGrowth #LearningInPublic

77

8 commenti

TestNG Annotations explained ! If you’ve ever been confused about which annotation runs when in TestNG… you’re not alone. I faced the same when I first started writing automation frameworks. Here’s the flow : • @BeforeSuite / @AfterSuite -> Runs only once for the entire suite. Perfect for global setup like DB connections, property files, or test data prep. • @BeforeTest / @AfterTest -> Runs once per <test> tag in testng.xml. Useful for setting up things specific to a test group. • @BeforeClass / @AfterClass -> Runs once before/after all methods in a class. Ideal for class-level setup (e.g., initializing WebDriver). • @BeforeMethod / @AfterMethod -> Runs before & after every single test method. Great for test preconditions & cleanup. • @Test -> The heart of your test suite – your actual test cases. If your tests behave unpredictably, check which annotation level your setup is tied to. Misusing @BeforeClass when you needed @BeforeMethod is one of the most common mistakes I’ve seen. ---------------------------------------------------- • Join Telegram Channel for daily job updates: • If you need help with job search, interview preparation, or anything related to QA. Feel free to connect with me on Topmate. #TestAutomation #SDET #TestNG #Java #AutomationTesting #TestingTips

105

1 commento

Exciting news! Qualitest Portugal is happy to announce its official association with the PSTQB – Portuguese Software Testing Qualifications Board. This entity represents ISTQB® in Portugal, the world's largest organization dedicated to #softwaretesting certification. This association marks a strategic advancement in our commitment to promote quality practices aligned with the highest international standards. By becoming a member of PSTQB, Qualitest Portugal strengthens its dedication to continuous training, professional certification, and active involvement in the national technical community.​​ ​Shai Liberman | Elad Levi | Cátia Carreira | Bruno Cardoso | Chloe Hibbert | Vijay Verghis | PSTQB - Associação Portuguesa de Testes de Software | ISTQB® - International Software Testing Qualifications Board #TechCertification #TestingExcellence #QAInnovation #ISTQB #Qualitest

124

1 commento

BDD is Often Just Glorified, Poorly Written User Stories and Test Scripts It is bad that too many teams adopt Gherkin syntax without the collaboration, missing the entire point. It is even worse when the QA is not part of the collaboration in User Story creation. But the worst thing is when the management insist on Cucumber implementation in the automation testing framework. The real value of Behavior-Driven Development is in the collaboration and conversation, not the Gherkin syntax, or in any tool. If you want a successful project - implement proper BDD - collaborative conversation that creates a shared understanding between product, development, and QA. #BDD #Agile #SoftwareDevelopment #QualityAssurance #TestAutomation #Collaboration

106

56 commenti

🚀 𝐓𝐞𝐬𝐭𝐍𝐆 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐖𝐢𝐭𝐡 𝐒𝐞𝐥𝐞𝐧𝐢𝐮𝐦 𝐓𝐞𝐬𝐭 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐓𝐞𝐬𝐭𝐍𝐆? TestNG (Test Next Generation) is a testing framework inspired by JUnit and NUnit but with more powerful features. 𝐖𝐡𝐲 𝐃𝐨 𝐖𝐞 𝐍𝐞𝐞𝐝 𝐓𝐞𝐬𝐭𝐍𝐆? - Flexible Annotations: Organize test code efficiently with annotations like @Test, @BeforeMethod, and @AfterMethod. - Parallel Testing: Run tests in parallel to save time, essential for large projects. - Data-Driven Testing: Easily test with multiple data sets using the @DataProvider annotation. - Test Configuration: Customize test execution with configurable suites, groups, and dependencies. - Reporting: Generate detailed HTML and XML reports for better insights. Seamless Integration: Works well with build tools like Maven and Gradle, and supports CI/CD pipelines for continuous testing. 𝐇𝐨𝐰 𝐭𝐨 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐞 𝐓𝐞𝐬𝐭𝐍𝐆 𝐰𝐢𝐭𝐡 𝐒𝐞𝐥𝐞𝐧𝐢𝐮𝐦 𝐉𝐚𝐯𝐚? 1. Add TestNG Dependency:   - If your Maven Project, add the following dependency in your `pom.xml` file:        <dependency>      <groupId>org.testng</groupId>      <artifactId>testng</artifactId>      <version>7.8.0</version>      <scope>test</scope>    </dependency> 2. Create a Test Class:   - Write a Selenium test case inside a class and annotate the test method with `@Test`. 3. Run the Test:   - Right-click on the test class in your IDE and choose `Run As > TestNG Test`.   - Alternatively, create a TestNG XML file to define your test suite and run it. 𝐖𝐡𝐚𝐭 𝐚𝐫𝐞 𝐭𝐡𝐞 𝐓𝐞𝐬𝐭𝐍𝐆 𝐇𝐨𝐨𝐤𝐬? TestNG hooks are special annotations that define the order in which test methods, configuration methods, and suites are executed. These hooks include: 1. @BeforeSuite / @AfterSuite: Executed before/after all tests in the suite. 2. @BeforeTest / @AfterTest: Executed before/after the test tag in the XML file. 3. @BeforeClass / @AfterClass: Executed before/after the first method in the class is invoked. 4. @BeforeMethod / @AfterMethod: Executed before/after each test method in the class. 5. @BeforeGroups / @AfterGroups: Executed before/after specified groups of tests run. 6. @BeforeClass / @AfterClass: Executed once before/after the first/last method in the current class. These hooks allow you to set up preconditions and perform clean-up activities in your test suite effectively. For the full code example, visit the link provided. ✅Follow Kushal Parikh for insightful content on Automation Testing! 🚀 𝐔𝐥𝐭𝐢𝐦𝐚𝐭𝐞 𝐐𝐀/𝐒𝐃𝐄𝐓 𝐃𝐢𝐠𝐢𝐭𝐚𝐥 𝐊𝐢𝐭 https://lnkd.in/dYPWn5xE 🚀 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧 𝐓𝐞𝐬𝐭𝐢𝐧𝐠 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞 𝐖𝐞𝐛𝐬𝐢𝐭𝐞𝐬 https://lnkd.in/dBzp5RAy 𝐇𝐚𝐩𝐩𝐲 𝐓𝐞𝐬𝐭𝐢𝐧𝐠! #testing #java #testng #qa #testingcommunity

90

3 commenti

"It works on my machine!" The five most dangerous words in software development. Developer: "Runs fine on my browser." Tester: "Great, send me the link." Developer: "http://localhost/test2" QA Team: enters the chat 🧑‍💻 This happens more often than we’d like to admit. The truth is: Developers build with a focus on features. Testers validate with a focus on users. QA teams ensure it all works in real environments, not just on one laptop. Software doesn’t succeed because it works on one machine. It succeeds when it works for everyone, everywhere. #QA #Testing #SoftwareTesting #Developers #BugLife #QualityAssurance #Teamwork

120

2 commenti

I’m pleased to share that I’ve developed a Web Automation Practice Website designed with #AI to help #QA engineers and automation testers strengthen their skills through hands-on practice. 🌐 Website: https://lnkd.in/dvJvdJkZ This site includes various web elements and scenarios, such as input fields, buttons, dropdowns, alerts, tables, and frames to support practice and experimentation with tools like Selenium, Playwright, and Cypress. The goal is to provide a simple practice environment for learners, professionals, and trainers in the field of test automation. I welcome feedback and suggestions from the community to enhance it further. Link - https://lnkd.in/dvJvdJkZ Thank you! #AutomationTesting #SoftwareTesting #TestAutomation #Selenium #Playwright #Cypress #QATraining #WebTesting #LearningByDoing #Tester #AI #SDET

595

63 commenti

Wondering how to automatically send your Cypress test execution report? 📧 #TechASip with Yagya Bhatta, Senior Software Engineer, as he provides a step-by-step guide to integrating Cypress email to send test execution to all the stakeholders automatically. Discover how the integration works, the tools involved, and how it can streamline communication and boost efficiency. 🌟 Read the full blog here 👉https://lnkd.in/dHY8fi5b #cypress #QA #QAAutomation #TechInsights #Leapfrogtechinsights

45

2 commenti

2 hours of focused testing every day for a week → much more effective than burning out with 12 hours on a weekend. Writing one solid bug report with clear steps and impact → much more valuable than logging five vague ones no one can reproduce. Debugging one flaky test till it’s fixed → much more useful than skipping over ten red marks in your pipeline. Rewriting the same automation flow with better structure → much more powerful than adding five new ones that no one maintains. Reading logs and tracing the issue end-to-end → much more insightful than just raising a ticket and moving on. Running a dry run before the actual test execution → much more efficient than discovering blockers mid-cycle. Reviewing your old test cases and improving them → much more productive than blindly adding new ones. A single conversation with a dev to clarify a feature → much more helpful than writing 20 assumptions in your test plan. Documenting your learnings after each release → much more effective than starting from scratch every time. Catching one missed edge case and fixing it → much more impressive than executing 100 cases that add no real value. Quality work doesn’t come from a last-minute rush. It comes from showing up daily, thinking clearly, and improving as you go. QA is not about how many test cases you wrote. It’s about how many problems you prevented. Consistency > Chaos Repost this if you agree. P.S. I'm Raghvendra, a QA-II at Amazon. I share real stories and practical lessons from my journey in QA and career growth. Follow along if that’s the path you’re on, too.

1.038

13 commenti

Experienced testers know the drill: retesting confirms a fix, but regression testing proves you didn't break anything else. But in the fast-paced world of CI/CD, how do you handle the sheer volume of both? How do you prioritize? And when do you draw the line between a selective re-run and a full-suite regression? This isn't just about a definition, it's about strategy. Our latest blog post dives into the subtle but crucial differences between regression testing and retesting, offering best practices tailored for complex, dynamic environments. We also touch on how AI can automate these tasks, allowing you to focus on more challenging test cases. Read the full blog: https://hubs.li/Q03LfXfn0 #SoftwareTesting #QAAutomation #TestStrategy #RegressionTesting #Retesting #ACCELQ

22

What if your tests could fix themselves and ship products faster? Software teams today define quality by delivering products with speed and precision, every single time. Do you find yourself struggling with: • Test scripts breaking from UI changes? • Slowed releases due to manual fixes? • Quality Engineers stuck debugging instead of innovating? With AI-driven self-healing test automation, you can: • Adapt tests to UI changes instantly • Keep CI/CD pipelines uninterrupted • Empower Quality Engineers as strategic innovators • Accelerate releases while ensuring quality Teams across industries are already slashing test maintenance and elevating quality with this approach. This is the first in our series on redefining Quality Engineering, and it starts here. ↗️ https://lnkd.in/gq8f9aum #TestAutomation #QualityEngineering #DevOps #CloudKaptan

42

Most teams run accessibility checks inside their tests. It works, but.... 🔴 Suites get slower 🔴 Failures get noisy 🔴 And you can still miss things like modals, dropdowns, or error states. In Cypress Accessibility, accessibility and functional testing don’t run on the same track. You test your app as usual, then we analyze the test replay. That way you gain: ✅ Fast test runs (no extra assertions slowing you down) ✅ Full coverage of every state your test touched ✅ Actionable reports with full-page snapshots tied to real interactions The result: more coverage, less flake, and a clearer view of what really needs fixing. All with no setup or code updates. Just record your tests. The full breakdown is here → https://bit.ly/4mWKtPm

40

🤔 Do all testers need to learn how to code so they can automate tests? Let's tune in to this week of #AutomationDecoded where Alex Martins shared his insights on the topic! According to Alex, ultimately, testing is about applying business knowledge to think up test scenarios. For test automation, QA teams can leverage low-code automation testing tools to do it. These tools can democratize testing for non-technical people, so everyone can join the QA process! #Katalon #KatalonStudio #AutomationTestingTools

22