As a solo developer/site owner,
I want to implement a simulated ticket purchasing system in the back-end of the festival app,
So that I can demonstrate the app's potential to handle e-commerce functionalities and enhance user interaction, even though actual transactions aren't processed.
Acceptance Criteria
Simulated Transactions: The system can simulate ticket selection, cart management, and checkout processes without real payment processing.
Data Handling: Simulated transactions are logged in the database, mimicking real purchase records.
API Interaction: The front-end can interact with back-end APIs to simulate adding tickets to a cart and checking out, providing a realistic user experience.
Tasks
[ ] Design a Simulated Payment Flow: Outline a simplified flow for ticket selection, adding to a cart, and "checking out" that doesn't involve real money or external payment services.
[ ] Extend the Database Schema: Adapt the database schema to include mock tables for tickets, simulated transactions, and cart items.
[ ] Create Mock APIs: Develop RESTful APIs that support the simulated ticket purchasing flow, including:
An API endpoint to list mock tickets.
An API endpoint to add/remove tickets from a simulated cart.
An API endpoint to simulate the checkout process.
[ ] Log Simulated Transactions: Ensure that each step in the mock purchase process is logged, similar to how real transactions would be recorded.
[ ] Front-End Integration (Optional): If applicable, ensure the front-end can consume these mock APIs to provide a seamless user experience, even in simulation.
JorgenDIF/PP4-Riot-Rythm-Festival#60
As a solo developer/site owner, I want to implement a simulated ticket purchasing system in the back-end of the festival app, So that I can demonstrate the app's potential to handle e-commerce functionalities and enhance user interaction, even though actual transactions aren't processed.
Acceptance Criteria
Tasks
[ ] Design a Simulated Payment Flow: Outline a simplified flow for ticket selection, adding to a cart, and "checking out" that doesn't involve real money or external payment services.
[ ] Extend the Database Schema: Adapt the database schema to include mock tables for tickets, simulated transactions, and cart items.
[ ] Create Mock APIs: Develop RESTful APIs that support the simulated ticket purchasing flow, including:
[ ] Log Simulated Transactions: Ensure that each step in the mock purchase process is logged, similar to how real transactions would be recorded.
[ ] Front-End Integration (Optional): If applicable, ensure the front-end can consume these mock APIs to provide a seamless user experience, even in simulation.