simplecov 0.19.0 → 0.21.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +49 -506
- data/README.md +45 -9
- data/doc/alternate-formatters.md +5 -0
- data/lib/simplecov.rb +19 -16
- data/lib/simplecov/configuration.rb +44 -18
- data/lib/simplecov/default_formatter.rb +20 -0
- data/lib/simplecov/defaults.rb +5 -2
- data/lib/simplecov/exit_codes/maximum_coverage_drop_check.rb +44 -11
- data/lib/simplecov/exit_codes/minimum_coverage_by_file_check.rb +26 -10
- data/lib/simplecov/file_list.rb +12 -6
- data/lib/simplecov/lines_classifier.rb +2 -2
- data/lib/simplecov/result.rb +2 -31
- data/lib/simplecov/result_merger.rb +121 -52
- data/lib/simplecov/source_file/line.rb +1 -1
- data/lib/simplecov/version.rb +1 -1
- metadata +20 -8
- data/CODE_OF_CONDUCT.md +0 -76
- data/CONTRIBUTING.md +0 -51
- data/ISSUE_TEMPLATE.md +0 -23
data/CODE_OF_CONDUCT.md
DELETED
@@ -1,76 +0,0 @@
|
|
1
|
-
# SimpleCov Code of Conduct
|
2
|
-
|
3
|
-
## Our Pledge
|
4
|
-
|
5
|
-
In the interest of fostering an open and welcoming environment, we as
|
6
|
-
contributors and maintainers pledge to making participation in our project and
|
7
|
-
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
-
size, disability, ethnicity, sex characteristics, gender identity and expression,
|
9
|
-
level of experience, education, socio-economic status, nationality, personal
|
10
|
-
appearance, race, religion, or sexual identity and orientation.
|
11
|
-
|
12
|
-
## Our Standards
|
13
|
-
|
14
|
-
Examples of behavior that contributes to creating a positive environment
|
15
|
-
include:
|
16
|
-
|
17
|
-
* Using welcoming and inclusive language
|
18
|
-
* Being respectful of differing viewpoints and experiences
|
19
|
-
* Gracefully accepting constructive criticism
|
20
|
-
* Focusing on what is best for the community
|
21
|
-
* Showing empathy towards other community members
|
22
|
-
|
23
|
-
Examples of unacceptable behavior by participants include:
|
24
|
-
|
25
|
-
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
-
advances
|
27
|
-
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
-
* Public or private harassment
|
29
|
-
* Publishing others' private information, such as a physical or electronic
|
30
|
-
address, without explicit permission
|
31
|
-
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
-
professional setting
|
33
|
-
|
34
|
-
## Our Responsibilities
|
35
|
-
|
36
|
-
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
-
behavior and are expected to take appropriate and fair corrective action in
|
38
|
-
response to any instances of unacceptable behavior.
|
39
|
-
|
40
|
-
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
-
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
-
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
-
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
-
threatening, offensive, or harmful.
|
45
|
-
|
46
|
-
## Scope
|
47
|
-
|
48
|
-
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
-
when an individual is representing the project or its community. Examples of
|
50
|
-
representing a project or community include using an official project e-mail
|
51
|
-
address, posting via an official social media account, or acting as an appointed
|
52
|
-
representative at an online or offline event. Representation of a project may be
|
53
|
-
further defined and clarified by project maintainers.
|
54
|
-
|
55
|
-
## Enforcement
|
56
|
-
|
57
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
-
reported by contacting the project team at simplecov.team@gmail.com. All
|
59
|
-
complaints will be reviewed and investigated and will result in a response that
|
60
|
-
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
-
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
-
Further details of specific enforcement policies may be posted separately.
|
63
|
-
|
64
|
-
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
-
faith may face temporary or permanent repercussions as determined by other
|
66
|
-
members of the project's leadership.
|
67
|
-
|
68
|
-
## Attribution
|
69
|
-
|
70
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
-
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
|
72
|
-
|
73
|
-
[homepage]: https://www.contributor-covenant.org
|
74
|
-
|
75
|
-
For answers to common questions about this code of conduct, see
|
76
|
-
https://www.contributor-covenant.org/faq
|
data/CONTRIBUTING.md
DELETED
@@ -1,51 +0,0 @@
|
|
1
|
-
## Reporting Issues
|
2
|
-
|
3
|
-
You can report issues at https://github.com/simplecov-ruby/simplecov/issues
|
4
|
-
|
5
|
-
Before you go ahead please search existing issues for your problem, chances are someone else already reported it.
|
6
|
-
|
7
|
-
To make sure that we can help you quickly please include and check the following information:
|
8
|
-
|
9
|
-
* Include how you run your tests and which testing framework or frameworks you are running.
|
10
|
-
- please ensure you are requiring and starting SimpleCov before requiring any application code.
|
11
|
-
- If running via rake, please ensure you are requiring SimpleCov at the top of your Rakefile
|
12
|
-
For example, if running via RSpec, this would be at the top of your spec_helper.
|
13
|
-
- Have you tried using a [`.simplecov` file](https://github.com/simplecov-ruby/simplecov#using-simplecov-for-centralized-config)?
|
14
|
-
* Include the SimpleCov version you are running in your report.
|
15
|
-
* If you are not running the latest version (please check), and you cannot update it,
|
16
|
-
please specify in your report why you can't update to the latest version.
|
17
|
-
* Include your `ruby -e "puts RUBY_DESCRIPTION"`.
|
18
|
-
* Please also specify the gem versions of Rails (if applicable).
|
19
|
-
* Include any other coverage gems you may be using and their versions.
|
20
|
-
|
21
|
-
Include as much sample code as you can to help us reproduce the issue. (Inline, repo link, or gist, are fine. A failing test would help the most.)
|
22
|
-
|
23
|
-
This is extremely important for narrowing down the cause of your problem.
|
24
|
-
|
25
|
-
Thanks!
|
26
|
-
|
27
|
-
## Making Contributions
|
28
|
-
|
29
|
-
To fetch & test the library for development, do:
|
30
|
-
|
31
|
-
$ git clone https://github.com/simplecov-ruby/simplecov.git
|
32
|
-
$ cd simplecov
|
33
|
-
$ bundle
|
34
|
-
$ bundle exec rake
|
35
|
-
|
36
|
-
If you want to contribute, please:
|
37
|
-
|
38
|
-
* Fork the project.
|
39
|
-
* Make your feature addition or bug fix.
|
40
|
-
* Add tests for it. This is important so I don't break it in a future version unintentionally.
|
41
|
-
* **Bonus Points** go out to anyone who also updates `CHANGELOG.md` :)
|
42
|
-
* Send me a pull request on GitHub.
|
43
|
-
|
44
|
-
## Running Individual Tests
|
45
|
-
|
46
|
-
This project uses RSpec and Cucumber. Individual tests can be run like this:
|
47
|
-
|
48
|
-
```bash
|
49
|
-
bundle exec rspec path/to/test.rb
|
50
|
-
bundle exec cucumber path/to/test.feature
|
51
|
-
```
|
data/ISSUE_TEMPLATE.md
DELETED
@@ -1,23 +0,0 @@
|
|
1
|
-
Howdy! Thanks for reporting an issue <3
|
2
|
-
|
3
|
-
Before you go ahead please search existing issues for your problem, chances are someone else already reported it.
|
4
|
-
|
5
|
-
To make sure that we can help you quickly please include and check the following information:
|
6
|
-
|
7
|
-
* Include how you run your tests and which testing framework or frameworks you are running.
|
8
|
-
- please ensure you are requiring and starting SimpleCov before requiring any application code.
|
9
|
-
- If running via rake, please ensure you are requiring SimpleCov at the top of your Rakefile
|
10
|
-
For example, if running via RSpec, this would be at the top of your spec_helper.
|
11
|
-
- Have you tried using a [`.simplecov` file](https://github.com/simplecov-ruby/simplecov#using-simplecov-for-centralized-config)?
|
12
|
-
* Include the SimpleCov version you are running in your report.
|
13
|
-
* If you are not running the latest version (please check), and you cannot update it,
|
14
|
-
please specify in your report why you can't update to the latest version.
|
15
|
-
* Include your `ruby -e "puts RUBY_DESCRIPTION"`.
|
16
|
-
* Please also specify the gem versions of Rails (if applicable).
|
17
|
-
* Include any other coverage gems you may be using and their versions.
|
18
|
-
|
19
|
-
Include as much sample code as you can to help us reproduce the issue. (Inline, repo link, or gist, are fine. A failing test would help the most.)
|
20
|
-
|
21
|
-
This is extremely important for narrowing down the cause of your problem.
|
22
|
-
|
23
|
-
Thanks!
|