Skip to main content

🧪 Release Smoke Suite

Environment: Demo/Production Schedule: Daily at 8:30 AM UK Time (2:00 AM IST)
Execution: GitHub Actions Workflow: .on-demand.release.smoke.yml

✅ Test Coverage Overview​

🔹 Test: Should not allow to proceed for Automation, BOT user​

Purpose: Ensure that BOT users are restricted from booking enquiry flow.
Expected Result: Navigation is blocked at Cloudflare validation or booking initiation.

🔹 Test: Should be able to create a new BookIn for a managed vehicle with Visn stock​

Purpose: Verify that a lease user can successfully create and submit a booking enquiry with VISN stock.
Expected Result: Booking enquiry is created and submitted without errors.

🔹 Test: Should be able to create a new walk-in enquiry for a managed vehicle​

Purpose: Validate the complete workflow of a walk-in enquiry lifecycle including job sheet, authorization, MOT, invoicing, and credit.
Expected Result: Walk-in enquiry (e.g., #3949) is successfully processed through all stages and closed with generated invoice and credit.

🔹 Test: Should be able to create a new walk-in enquiry and progress to credit generation​

Purpose: Test the end-to-end journey of a walk-in enquiry including MOT submission and invoice/credit generation.
Expected Result: Walk-in enquiry (e.g., #3950) reaches completion and both invoice and credit documents are generated.

🔹 Test: Create a new sub-customer and vehicle​

Purpose: Validate sub-customer and vehicle creation forms, including inline validations and successful save messages.
Expected Result: Sub-customer and vehicle are created, and toast notifications confirm successful saves.

🔹 Test: V-Supplier - Create walk-in enquiry with driver details​

Purpose: Ensure a supplier user can create a walk-in enquiry using a newly added vehicle with inline driver details and progress it fully.
Expected Result: Enquiry (e.g., #3952) is successfully processed end-to-end, invoice and credit PDFs are auto-uploaded to documents, and event logs are correctly generated.

🔹 Test: Walk-In Enquiry Without Driver Details for Newly Added Vehicle​

Purpose: To validate that a supplier user can create a walk-in enquiry for a newly added VISN stock vehicle without entering driver details.
Expected Result: Walk-in enquiry should be created successfully and a confirmation message should be displayed.

🔹 Test: Delete Vehicle and Subcustomer​

Purpose: To verify that a supplier user can delete a vehicle and its associated subcustomer after walk-in enquiry creation.
Expected Result: Vehicle and subcustomer should be deleted successfully without errors.

🔹 Test: Walk-In Enquiry via API - Create Sub-customer, Vehicle, and Enquiry​

Purpose: To ensure walk-in enquiry can be created via API by first creating a subcustomer and a vehicle, and then triggering the enquiry creation.
Expected Result: Subcustomer and vehicle should be created successfully, and the enquiry should be accepted by the system with a successful API response.

🔹 Test: Book-In Enquiry via API - Create Entities and Progress to Credit Generation​

Purpose: To validate the complete book-in enquiry process via API including subcustomer and vehicle creation, enabling rules, and progressing the enquiry up to credit generation.
Expected Result: All entities should be created successfully, booking should be submitted and accepted, and system should confirm credit generation readiness.