Skip to content

[PM-18502] jest and rust coverage upload separated as one step #14286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

mzieniukbw
Copy link
Contributor

@mzieniukbw mzieniukbw commented Apr 15, 2025

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-18502

📔 Objective

This change prevents the coverage to be uploaded twice in different times (since jest tests takes 8-10 minutes, while rust up to 2 minutes), which results in email, notification being sent and commend made in PR that coverage is near 0% (since rust finishes first, which is minority of all coverage).
Jest and rust coverage upload is now separated as one step.

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

Copy link
Contributor

github-actions bot commented Apr 15, 2025

Logo
Checkmarx One – Scan Summary & Details87920df9-7317-4a0d-a8ee-ee4c7897d83c

New Issues (1)

Checkmarx found the following issues in this Pull Request

Severity Issue Source File / Package Checkmarx Insight
MEDIUM CVE-2025-32379 Npm-koa-2.15.4
detailsDescription: Koa is expressive middleware for Node.js using ES2017 async functions. In koa versions prior to 2.16.1 and 3.x prior to 3.0.0-alpha.5, passing untr...
Attack Vector: NETWORK
Attack Complexity: HIGH

ID: BWOz040uNb6vTZEaF5xJdZTs0Gxx6zL3MmFCTPlKCfQ%3D
Vulnerable Package

Copy link

codecov bot commented Apr 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.88%. Comparing base (cb86948) to head (f36eb16).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #14286   +/-   ##
=======================================
  Coverage   36.87%   36.88%           
=======================================
  Files        3213     3213           
  Lines       92648    92648           
  Branches    16632    16632           
=======================================
+ Hits        34166    34169    +3     
+ Misses      56061    56058    -3     
  Partials     2421     2421           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mzieniukbw mzieniukbw marked this pull request as ready for review April 16, 2025 07:23
@mzieniukbw mzieniukbw requested a review from a team as a code owner April 16, 2025 07:23
@mzieniukbw mzieniukbw requested a review from justindbaur April 16, 2025 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant