Spryker Cypress E2E Assistant GPT

Last updated:
Edit on GitHub

Before using AI tools, consult with your legal department.

The Spryker Cypress E2E Assistant, powered by GPT technology, is designed to help developers and QA engineers implement, configure, and optimize Cypress for end-to-end (E2E) testing in Spryker projects. The assistant leverages a knowledge base containing the Spryker Cypress Boilerplate repository and other assets to provide accurate, example-driven guidance, ensuring best practices and optimized testing workflows.

Use case

User profile: Anna is a QA engineer at an e-commerce company that uses Spryker’s B2B marketplace. She is responsible for maintaining the quality of the platform by writing and running Cypress tests to ensure smooth functionality after every deployment.

Problem: Anna needs a tool to assist her in writing Cypress tests, integrating them into CI pipelines, and maintaining consistency in testing structures and best practices.

Solution with the Spryker Cypress E2E Assistant

  • Understanding E2E testing: The assistant helps understand the fundamentals of E2E testing, why it’s crucial in ensuring system reliability, and how to determine what to cover with E2E tests to ensure comprehensive test coverage for critical user flows.

  • Best practices: The assistant provides best practices for maintaining consistent, efficient Cypress tests, including recommendations on structuring tests, writing reusable custom commands, and ensuring scalability of tests as the project grows.

  • Step-by-step guidance: Provides detailed, step-by-step instructions on setting up Cypress and integrating it into a Spryker environment. The assistant offers direct guidance from the Spryker Cypress Boilerplate, helping configure test structures and execute tests efficiently.

  • Code snippet assistance: Offers specific Cypress test examples and accurate, ready-to-use real-world snippets from the Spryker Cypress Boilerplate repository.

Access

Spryker Cypress E2E Assistant GPT

Early Access Program

As part of Spryker’s Early Access Program, we use your feedback to refine early-access features that are still under development. This section describes how the program works and how you can participate.

Program goals

  • Integration and compatibility testing: Evaluate how well the tool integrates into various Spryker projects.
  • Identify gaps and issues: Because this is a third-party tool using another third-party tool, Spryker is not in control of how ChatGPT behaves. There may be unexpected issues and unsatisfactory results which we need to track and collect to understand if they can be improved upon.
  • Understand user onboarding and learning curve:
    • Evaluate if the tool can be successfully used by engineers with varying levels of expertise.
    • Assess whether engineers can effectively use the tool without extensive training and derive valuable insights for testing processes.
  • Drive adoption: Promote the usage of comprehensive functional testing checklists and dependency analysis, providing an easy entry point for users.
  • Gather case studies and success stories: Gather case studies and success stories of early users who derived significant value from the tool.

Your feedback will help us understand if we are meeting these goals effectively.

Early Access Program

Early Access Program enables real-world testing of our product’s new capabilities and tools. This helps us refine and improve the product based on feedback from partners and customers.

Early access release GPTs may be unsupported and are subject to change, potentially leading to changes or discontinuation before a general availability release.

Participate

You can start participating by using the tool and providing feedback.

Provide feedback

You can provide feedback through surveys, interviews, and Feedback Exchange Portal.

Iteration and improvement

Based on your feedback, we will continuously improve Spryker GPTs.

Program shutdown activities

We will announce the program shutdown two weeks in advance. After that, we will transition the tool to a General Availability Release, or discontinue it based on our analysis. Regardless of the outcome, we will communicate the next steps, learnings, and insights from the program.