Documentation for proj-gauchoride

• Source Repo: https://github.com/ucsb-cs156/proj-gauchoride
• Github Actions: https://github.com/ucsb-cs156/proj-gauchoride/actions

Documentation

Backend	Frontend
Javadoc	Storybook
javadoc	storybook

Test Coverage

Backend		Frontend
Jacoco	Pitest	Coverage	Stryker
jacoco	pitest	coverage	stryker

Open Pull Requests

Documentation

Pull Request			Backend	Frontend
PR	Branch	Author	Javadoc	Storybook
PR 122	s24-5pm-8	pconrad	javadoc	storybook
PR 121	s24-5pm-7	pconrad	javadoc	storybook
PR 120	s24-5pm-6	pconrad	javadoc	storybook
PR 119	s24-5pm-5	pconrad	javadoc	storybook
PR 86	cal-spike	pconrad	javadoc	storybook
PR 85	me-SMS-SPIKE	pconrad	javadoc	storybook

Test Coverage

Pull Request			Backend		Frontend
PR	Branch	Author	Jacoco	Pitest	Coverage	Stryker
PR 122	s24-5pm-8	pconrad	jacoco	pitest	coverage	stryker
PR 121	s24-5pm-7	pconrad	jacoco	pitest	coverage	stryker
PR 120	s24-5pm-6	pconrad	jacoco	pitest	coverage	stryker
PR 119	s24-5pm-5	pconrad	jacoco	pitest	coverage	stryker
PR 86	cal-spike	pconrad	jacoco	pitest	coverage	stryker
PR 85	me-SMS-SPIKE	pconrad	jacoco	pitest	coverage	stryker

Notes

If links in the PR tables don’t work, note the following:

• Backend links may not be updated for PRs that do not touch the backend code.
• Frontend links may not be updated for PRs that do not touch the frontend code.
• If a link doesn’t work when you expect that it should, check that the appropriate Github Actions workflow completed successfully.
• You can also check the contents of the gh-pages branch of this repo to see if they were updated with the appropriate directory.
• Note that the pitest runs that are triggered by PRs and by workflow 2 compute incremental pitest results based on stored history. It is rare, but this may occasionally be different from the results when doing a full pitest run from scratch, which is done every time a push is made to the main branch (for example, when merging a PR).