- 
                Notifications
    You must be signed in to change notification settings 
- Fork 39
Move EUnit to CT #115
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
Move EUnit to CT #115
Conversation
| 
 | 
65e69a9    to
    a938b10      
    Compare
  
    | 
 Codecov ReportAll modified and coverable lines are covered by tests ✅ 
 ❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@            Coverage Diff             @@
##             main     #115      +/-   ##
==========================================
- Coverage   76.30%   76.08%   -0.23%     
==========================================
  Files          12       12              
  Lines         764      740      -24     
==========================================
- Hits          583      563      -20     
+ Misses        181      177       -4     ☔ View full report in Codecov by Sentry. | 
a938b10    to
    6b8564c      
    Compare
  
    | 
 | 
| 
 | 
| Is anything lacking for this one to get merged? I can then rebase and update the other ones. | 
| Only issue with these from my perspective has been their size (even if it looks like many of the commits are the same across the PRs, its still that getting one merged means being confident with changes to a lot of files) and I just haven't had the time to look them over close enough to feel comfortable. | 
| I understand. I'll try to rebase/squash, etc. to ease review and maybe that can remove some commits that moved back and forth... @tsloughter, I think I did what I wanted already, in all the pull requests I have opened. The first one needing merge will be #114, so the other ones can "inherit" the new maintenance range and updates to CI files. | 
ac178c4    to
    98a4536      
    Compare
  
    | Moved to draft. These don't need to be reviewed before #114, after which I'll rebase. | 
98a4536    to
    198a6c9      
    Compare
  
    - deps and ebin are rebar 2 - ignore *.beam is not required, since _build - .eunit is legacy - pre-hook lint (for eunit) is removed and made explicit in the CI file - main.yml is tweaked to run static analysis first and tests later
Notice the use of README.md from the linked `priv` folder Files were mostly renamed and then: - added init/end_per_suite (from setup/teardown) - added init/end_per_testcase (from elli_test_) - removed _test suffix from exported function names - moved rebar.config test options to test profile - added a shareable (example + tests) symbolic link, used as filename:join(code:priv_dir(elli), "README.md") for single reference...
b5171a0    to
    9fe89e7      
    Compare
  
    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.
We go from eunit+dialyzer to xref+dialyzer+lint+ct+cover
Note: eunit was doing lint, as per rebar.config, but it's probably better to have it explicitly as a CI step.
Closes #101.
Depends on the CI file updates from #114, so shall be rebased and updated (if required) after that one.
In CT (this pull request):
In EUnit (
main)I tracked the differences for the
elli_httpmodule and they're only related to the missing test code (7 lines in the previous code). Inelli_testthis is not noticeable because we covered 100% and now cover 100% still...From the commit notes: