Skip to content
This repository was archived by the owner on Apr 7, 2026. It is now read-only.

Increase the code coverage#3

Open
dhAlcojor wants to merge 10 commits into
mainfrom
feature/code-coverage
Open

Increase the code coverage#3
dhAlcojor wants to merge 10 commits into
mainfrom
feature/code-coverage

Conversation

@dhAlcojor
Copy link
Copy Markdown
Owner

No description provided.

Daniel H. Alcojor added 2 commits August 19, 2024 12:54
Added push triggers for the main, develop, feature, and bugfix branches in the GitHub CI workflow. This ensures that any changes pushed to these branches will automatically initiate the CI process, maintaining continuous integration and testing standards.
Enhanced unit test to verify that the health bars display the correct initial health values. Modified the HTML to include class identifiers for left and right health bars, facilitating easier DOM element selection in tests.
@vercel
Copy link
Copy Markdown

vercel Bot commented Aug 19, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
comic-fight ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 19, 2024 0:47am

Updated the CI workflow name for clarity and consistency. Also added a build status badge to the README for better visibility of the CI status.
Daniel H. Alcojor added 2 commits August 19, 2024 13:15
Moved global coverage threshold checks from the top-level configuration to the coverage reporter settings. This change ensures that the checks are applied correctly during the coverage reporting phase.
This change eliminates the push trigger to streamline the workflow and rely solely on pull_request events for CI runs. This should reduce unnecessary CI executions and optimize resource usage.
Updated the Karma configuration to include the "coverage" reporter. This change ensures that code coverage reports are generated alongside the existing progress and HTML reporters, aiding in better analysis and testing of the project's codebase.
Changed the preprocessor configuration in karma.conf.js to include TypeScript files from the 'app' directory instead of 'src'. This ensures that code coverage reports are generated for the correct directory.
Updated the Karma configuration to explicitly define the file type as TypeScript for test files. Added the `--code-coverage` flag to the CI test script to generate code coverage reports during continuous integration runs.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant