Skip to content
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

Node fun test improvements III #9185

Merged
merged 3 commits into from
Sep 24, 2024
Merged

Conversation

fviernau
Copy link
Member

Clean up organization of expected result files.

@fviernau fviernau requested a review from a team as a code owner September 23, 2024 16:19
Copy link

codecov bot commented Sep 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.10%. Comparing base (442b553) to head (d0db7ff).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #9185   +/-   ##
=========================================
  Coverage     67.10%   67.10%           
  Complexity     1187     1187           
=========================================
  Files           240      240           
  Lines          7908     7908           
  Branches        914      914           
=========================================
  Hits           5307     5307           
  Misses         2233     2233           
  Partials        368      368           
Flag Coverage Δ
funTest-docker 59.82% <ø> (ø)
funTest-non-docker 34.49% <ø> (ø)
test 36.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@fviernau fviernau force-pushed the node-fun-test-improvements-iii branch 2 times, most recently from ef0fe4b to 88ae698 Compare September 24, 2024 06:52
@sschuberth
Copy link
Member

FYI, NpmFunTest fails with

java.io.FileNotFoundException: /workspace/plugins/package-managers/node/src/funTest/assets/projects/synthetic/npm/npm/package-lock-expected-output.yml (No such file or directory)

Use a dedicated expected result file for each respective test, to allow
for maintaining them independently.

Signed-off-by: Frank Viernau <frank_viernau@epam.com>
Consistently use `expected-output` as suffix, and align the name of the
expected result for skipping scope excludes with
`yarn2-project-with-lockfile-skip-excluded-scopes-expected-output.yml`.

Signed-off-by: Frank Viernau <frank_viernau@epam.com>
Reduce the repetition a bit.

Signed-off-by: Frank Viernau <frank_viernau@epam.com>
@fviernau fviernau force-pushed the node-fun-test-improvements-iii branch from 88ae698 to d0db7ff Compare September 24, 2024 09:21
@fviernau fviernau enabled auto-merge (rebase) September 24, 2024 09:35
@fviernau fviernau merged commit 9860496 into main Sep 24, 2024
23 checks passed
@fviernau fviernau deleted the node-fun-test-improvements-iii branch September 24, 2024 10:42
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.

2 participants