testing-and-ci

Automating CI/CD workflows for backend and frontend testing involves triggering automated test suites during development phases like PRs. This Skill uses JUnit, Mockito, and Spring Boot for backend, alongside Vitest and Playwright for frontend and E2E coverage.

A smoke test in a CI pipeline provides pre-release testing of crucial operational workflows to ensure stability. You need smoke testing to verify core functionality before merging feature updates or deploying releases.

Yes, you can use Playwright and Vitest for frontend test automation alongside Spring Boot. This Skill integrates these frontend testing frameworks with backend tools like JUnit and Mockito to ensure comprehensive testing coverage across modules.

To run smoke tests before merging feature updates, execute the `make smoke-test` command. This triggers the automated testing workflows to verify crucial operational paths and maintain code reliability before integration.

The best way to ensure consistent testing standards across CI pipelines is to enforce defined testing conventions and rules. This Skill facilitates standard test naming and execution to maintain consistency in code quality and automate CI processes.

Yes, JUnit works with Mockito and AssertJ for backend integration testing. This Skill automates backend test execution using these specific frameworks to validate code reliability and ensure comprehensive testing coverage within your development pipeline.