nofusscomputing / nofusscomputing/centurion_ui
Backend testing module
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 20
Description
Testing of a UI against a backend is required for countless reasons.
Details
Create as part of the UI package, a set of backend tests that have the following workflow:
-
Fetches navigation
-
Ensure Navigation is valid
-
UI works as intended
-
Navigates to all endpoints within navigation
- Ensure no console errors
- Ensure Data (HTTP/GET) is valid
- Ensure Metadata (HTTP/OPTIONS) is valid
-
-
Pages Speed tests
-
Navigates to all endpoints within navigation
- Ensure loads in desired timeframe
- Enables comparison of previous builds/releases
-
-
Tasks
- Add each of the tests as a reusable module that devs can run against their backend(s).
- 🧪 Ensure that the UI itself runs these tests against the test data.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the UI package and map the requested workflow from fetching navigation through endpoint checks and page-speed tests. Define reusable modules that validate navigation, UI behavior, console output, HTTP GET and OPTIONS data, and timing comparisons, then run them against the UI's test data to confirm the workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100