-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
taxonomy: added changes from laralem #8312
Conversation
Codecov Report
@@ Coverage Diff @@
## main #8312 +/- ##
=======================================
Coverage 47.06% 47.07%
=======================================
Files 109 109
Lines 20991 20991
Branches 4739 4739
=======================================
+ Hits 9880 9881 +1
Misses 9942 9942
+ Partials 1169 1168 -1 see 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
It was related to:
I understand that it is related to the subroutine compare_to_expected_results in lib/ProductOpener/Test.pm For now, I will comment fr: and es: for nitrate |
@benbenben2 the expected test results can be updated automatically, by running make update_tests_results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks a lot for updating the original PR! :)
I will try by myself and learn :) |
8f59bde
to
0b3a746
Compare
Kudos, SonarCloud Quality Gate passed! |
@stephanegigandet So far, from my side. Running in Gitpod. Running:
After couple of minutes, it results to (not sure if it is because I am on gitpod, seems related to timeout of something...)
I aslo tried to follow guidelines from "how-to-write-and-run-tests.md", and tried: Is it correct command? (Makefile file does not contain "make unit-test" but "make test-unit"). Hence, I also tried: I eventually could see that nitrate appeared in both ES and FR files. Then, commit and pushed. It result in new errors:
And here I'm stuck because changes are related to these nutrients in the error messages. But changes are for PT... |
@benbenben2 well the tests seem to be passing now, so we can merge |
trying to re-do the PR #5160 from @laralem... after 2 years!
Due to the evolution of the file for the last 2 years, the following changes from the previous PR could not be added: