/
Webinar 2: From Manual QA to Automation Engineer Using AI (BlinqIQ)

Webinar 2: From Manual QA to Automation Engineer Using AI (BlinqIQ)

Company

BlinqIO Demonstrated an AI-driven test automation platform.

Objective of the Webinar

The primary goal was to illustrate how Generative AI can empower manual testers to quickly transition into automation engineers. The presenters demonstrated

  • How AI can record manual testing flows and produce maintainable, open-source code.

  • Ways AI handles UI changes (self-healing) and integrates with CI/CD pipelines.

  • The strategic value of reducing manual effort, accelerating release cycles, and improving ROI.

Presenter of the Webinar

  • Tal (20+ years in software testing, previously co-founded a test automation platform.)

  • Sapneesh (Head of QA at Blinq IO)

  • Joe (Moderator)

Brief Summary of the Webinar

  • Introduction to AI in Testing

    • Described modern testing challenges: complex UIs, frequent releases, high maintenance costs.

    • Emphasized that Generative AI can create and maintain test automation code, reducing manual workload.

  • Live Demo (BlinqIO)

    • Demonstrated how a manual tester’s clicks are automatically converted into code (Playwright).

    • Showed “self-healing” capabilities, where AI updates scripts when the UI changes.

    • Highlighted integration with CI/CD tools for continuous testing.

  • Benefits for Manual Testers

    • No coding expertise required to produce or maintain test scripts.

    • Ability to add assertions, handle multi-factor authentication, random test data, and more.

  • Q&A

    • Addressed data privacy, performance testing, advanced configurations, and synergy with existing tools like JIRA.

Features and Technical Aspects Discussed

  • AI-Driven Recording

    • Captures user flows in real-time, generating business-level descriptions and code (Playwright, JavaScript/TypeScript).

  • Self-Healing / Maintenance

    • AI autonomously updates scripts when UIs or application flows change.

  • Data-Driven Testing

    • Integrates with CSVs, APIs, or random data generation for robust test coverage.

  • CI/CD Integration

    • Works with GitHub Actions, Jenkins, Azure DevOps, etc., enabling automated nightly or on-demand runs.

  • Analytics and Reporting

    • Provides detailed screenshots, logs, and root-cause analysis for failed tests.

  • Open-Source Code

    • Users retain full access to generated Playwright code, minimizing vendor lock-in.

  • Multilingual and Multi-Platform Support:

    • AI can generate test automation code for web, mobile (iOS and Android), and multilingual applications.

  • Parallel Execution:

    • Tests can be executed in parallel across multiple environments.

  • BDD (Behavior-Driven Development):

    • AI generates test scenarios in a structured BDD format.

How GoTestPro Can Compete

Given that GoTestPro offers a similar AI-driven approach, it can

  • Highlight Self-Healing Strengths

    • Demonstrate robust maintenance capabilities and advanced UI change handling.

  • Focus on Usability

    • Provide a user-friendly interface for non-technical testers.

  • Leverage CI/CD Integration

    • Showcase seamless pipelines and quick feedback loops.

  • Open-Source or Flexible Codebase

    • Emphasize code ownership and minimal vendor lock-in.

  • Address Enterprise Needs

    • Offer on-premises or private cloud deployments, ensuring data privacy and compliance.

From Manual QA to Automation Engineer Using AI - Demo Screenshots

BlinqIO-2-1-20250312-113130.png
BlinqIO-2-2-20250312-113238.png
BlinqIO-2-3-20250312-113514.png
BlinqIO-2-4-20250312-113715.png
BlinqIO-2-5-20250312-113836.png

 

Question and Answer

1. How does AI help manual testers become automation engineers without coding knowledge?

Answer: AI can translate manual test flows into automated test scripts by generating code (e.g., in Playwright or Selenium) and creating structured test descriptions (e.g., Gherkin BDD). It handles locators, parameterization, and maintenance autonomously, eliminating the need for manual testers to learn programming.

2. Can AI autonomously update test scripts when the UI changes?

Answer: Yes. AI analyzes UI changes (e.g., field additions/removals) and updates the test code automatically. It provides explanations (e.g., screenshots) for review, allowing manual testers to approve/reject changes without coding expertise.

3. How does AI handle test maintenance compared to traditional tools like Selenium?

Answer: Unlike Selenium, which fails on UI changes, AI understands the business logic of the test and autonomously adjusts locators and workflows. It regenerates stable code without human intervention.

4. Can AI generate negative or edge-case test scenarios?

Answer: Yes. AI can analyze requirements or existing tests to suggest negative/edge-case scenarios (e.g., invalid inputs) based on plain English prompts or JIRA tickets.

5. How does AI handle multi-factor authentication (MFA) in tests?

Answer: AI supports MFA via:

  • Time-based OTP (e.g., Google Authenticator) using generator keys.

  • Email OTP by accessing a dedicated inbox.

  • Session reuse for SSO logins.

6. Does AI reuse existing code for common steps (e.g., login)?

Answer: Yes. AI identifies repeated steps (e.g., login) and reuses their implementations across tests, avoiding duplication and adhering to coding best practices.

7. What test frameworks/languages does AI support?

Answer: Currently JavaScript/TypeScript (Playwright, Cucumber JS). Python support is planned for 2025.

8. Can AI integrate with CI/CD pipelines?

Answer: Yes. Tests can run in CI/CD tools (e.g., Jenkins, GitHub Actions) with commands for execution and reporting.

9. How does AI manage test data (e.g., unique fields)?

Answer: AI can:

  • Generate randomized data (e.g., phone numbers) using libraries like Faker.

  • Pull data from CSV files or APIs.

  • Parameterize inputs in Gherkin files.

10. Does AI support non-English applications?

Answer: Yes. Tests recorded in English can run on multilingual UIs (e.g., French/German) by leveraging stable locators.

11. Can AI test APIs or databases?

Answer:

  • APIs: Yes, AI can call APIs and use responses in UI tests.

  • Databases: Supports Oracle/MySQL for validations (e.g., UI vs. database checks).

12. Does AI create performance tests?

Answer: No, it currently focuses on functional testing. Parallel execution provides timing insights but not load testing.

13. Is the tool on-premises or cloud-based?

Answer: Both. Options include SaaS (shared/single-tenant) and on-premises deployments.

14. How does AI compare to record-and-playback tools?

Answer: Unlike traditional tools, AI:

  • Generates open-source code (e.g., Playwright).

  • Provides business-level test descriptions.

  • Autonomously maintains tests.

15. Can AI file bug reports for failed tests?

Answer: Yes, if integrated with JIRA/Monday. It auto-creates tickets with logs and reports.