Documentation for proj-frontiers

• Source Repo: https://github.com/ucsb-cs156/proj-frontiers
  • gh-pages: https://github.com/ucsb-cs156/proj-frontiers/tree/gh-pages
• Github Actions: https://github.com/ucsb-cs156/proj-frontiers/actions

Documentation

Backend	Frontend (Storybook/Chromatic)
javadoc	storybook	build info

Test Coverage

Backend		Frontend
Jacoco	Pitest	Coverage	Stryker
jacoco	pitest	coverage	stryker

Open Pull Requests

Documentation for PRs

Pull Request			Backend	Frontend (Storybook/Chromatic)
PR	Branch	Author	Javadoc	storybook	build info
PR 624	dk-errorhandling	DerekKirschbaum	javadoc	chromatic sb	build info
PR 623	dk-updatejobs	DerekKirschbaum	javadoc	chromatic sb	build info
PR 615	dp-canvas-token-enc	divyanipunj	javadoc	chromatic sb	build info
PR 613	Division7-patch-2	Division7	javadoc	chromatic sb	build info
PR 605	dj-rateLimitTracking	Division7	javadoc	chromatic sb	build info
PR 567	dj-simplifiedDockerfile	Division7	javadoc	chromatic sb	build info

Test Coverage for PRs

Pull Request			Backend		Frontend
PR	Branch	Author	Jacoco	Pitest	Coverage	Stryker
PR 624	dk-errorhandling	DerekKirschbaum	jacoco	pitest	coverage	stryker
PR 623	dk-updatejobs	DerekKirschbaum	jacoco	pitest	coverage	stryker
PR 615	dp-canvas-token-enc	divyanipunj	jacoco	pitest	coverage	stryker
PR 613	Division7-patch-2	Division7	jacoco	pitest	coverage	stryker
PR 605	dj-rateLimitTracking	Division7	jacoco	pitest	coverage	stryker
PR 567	dj-simplifiedDockerfile	Division7	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).