Membrane Backend: A centralized authentication service for Single Sign-On (SSO) enabling seamless token-based email verification across multiple client applications.
MIT License
1
stars
0
forks
source link
Implement Static Testing Page to Simplify Membrane Development Workflow #43
Currently, Membrane's architecture is split into two repositories: frontend and backend. While this separation has its advantages, it makes the testing process cumbersome as developers have to launch and manage multiple projects.
To simplify this, we propose to implement a static testing page within the Membrane project. This page would mock the frontend functionalities required for testing the backend, eliminating the need to run the entire frontend just for testing purposes.
Acceptance Criteria
The static page should mimic the essential functionalities of the frontend required for backend testing.
It should be easily accessible to developers without affecting the main application flow.
Should be documented on how to utilize this static page for testing.
Notes
The goal is to speed up the development and testing workflow by reducing the overhead of running multiple projects.
Tasks
Design the layout of the static page.
Implement the essential frontend functionalities in the static page.
Description
Currently, Membrane's architecture is split into two repositories: frontend and backend. While this separation has its advantages, it makes the testing process cumbersome as developers have to launch and manage multiple projects.
To simplify this, we propose to implement a static testing page within the Membrane project. This page would mock the frontend functionalities required for testing the backend, eliminating the need to run the entire frontend just for testing purposes.
Acceptance Criteria
Notes
Tasks