team02-f24-00

Documentation

Backend	Frontend (Storybook/Chromatic)
javadoc	storybook	build info

Backend		Frontend
Jacoco	Pitest	Coverage	Stryker
jacoco	pitest	coverage	stryker

Pull Request			Backend	Frontend (Storybook/Chromatic)
PR	Branch	Author	Javadoc	storybook	build info
PR 123	sk-Articles-fixtures	Division7	javadoc	chromatic sb	build info
PR 122	pc-commits-e2e-tests	pconrad	javadoc	chromatic sb	build info
PR 121	pc-commits-integration-tests	pconrad	javadoc	chromatic sb	build info
PR 115	Hongrui-UCSBOrganization	raysujf	javadoc	chromatic sb	build info
PR 75	Jenil-RecommendationRequestsFixtures	jenil-prajapati	javadoc	chromatic sb	build info

Pull Request			Backend		Frontend
PR	Branch	Author	Jacoco	Pitest	Coverage	Stryker
PR 123	sk-Articles-fixtures	Division7	jacoco	pitest	coverage	stryker
PR 122	pc-commits-e2e-tests	pconrad	jacoco	pitest	coverage	stryker
PR 121	pc-commits-integration-tests	pconrad	jacoco	pitest	coverage	stryker
PR 115	Hongrui-UCSBOrganization	raysujf	jacoco	pitest	coverage	stryker
PR 75	Jenil-RecommendationRequestsFixtures	jenil-prajapati	jacoco	pitest	coverage	stryker

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).