| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
On the coverage.py metacov, this makes the HTML 5% smaller.
|
| |
|
|
|
|
|
|
|
|
|
| |
Will fix:
https://github.com/nedbat/coveragepy/security/code-scanning/3
https://github.com/nedbat/coveragepy/security/code-scanning/4
(though tbh, not sure how to close those as fixed?)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It turns out that str.splitlines() will break text on some characters
that file.readline() does not! Use readline() to read source files the
same way that Python does.
|
|
|
|
| |
un-executed, white space, time stamp.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Eight fewer sub-processes
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Originally I used setup_test because something went wrong when I used setUp. I
wrote https://github.com/pytest-dev/pytest/issues/8424 about it. There they say
to use `-p no:nose` to disable nose interpretation.
But now I simply went back to setUp, and all seems well? Not sure what changed,
but using the expected name is better.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
.. and also add trailing commas where needed to remove ambiguity.
I used semgrep with this config:
```
rules:
- id: implicit-string-concatenation
pattern: |
"$X" "$Y"
languages:
- python
message: string cat BAD
severity: INFO
```
Running it showed this:
```
$ semgrep --config=../lab/string-cat.yml coverage tests doc ci igor.py setup.py __main__.py
Running 1 rules...
setup.py
severity:info rule:lab.implicit-string-concatenation: string cat BAD
128: 'https://tidelift.com/subscription/pkg/pypi-coverage'
129: '?utm_source=pypi-coverage&utm_medium=referral&utm_campaign=pypi'
tests/test_api.py
severity:info rule:lab.implicit-string-concatenation: string cat BAD
319: "!coverage.py: This is a private format, don't read it directly!"
320: '{"lines":{"/private/tmp/foo.py":[1,5,2,3]}}'
tests/test_html.py
severity:info rule:lab.implicit-string-concatenation: string cat BAD
614: ('<span class="key">if</span> <span class="num">1</span> '
615: '<span class="op"><</span> <span class="num">2</span>'),
--------------------------------------------------------------------------------
616: (' <span class="nam">a</span> '
617: '<span class="op">=</span> <span class="num">3</span>'),
--------------------------------------------------------------------------------
665: ('<span class="key">if</span> <span class="nam">x</span> '
666: '<span class="op"><</span> <span class="num">2</span>'),
--------------------------------------------------------------------------------
667: (' <span class="nam">a</span> <span class="op">=</span> '
668: '<span class="num">3</span>'),
--------------------------------------------------------------------------------
949: ('<span class="key">if</span> <span class="num">1</span> '
950: '<span class="op"><</span> <span class="num">2</span>'),
--------------------------------------------------------------------------------
951: (' <span class="nam">a</span> <span class="op">=</span> '
952: '<span class="num">3</span>'),
ran 1 rules on 134 files: 8 findings
```
This wasn't all of the instances, so I wrote a bug report: https://github.com/returntocorp/semgrep/issues/4184
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- highlights weren't showing
- anchored lines were not visible
- some j/k motions were broken
- clicking the big buttons at the top didn't work
|
|
|
|
|
| |
Those have to be scrubbed too. I'm not sure why it's sometimes there, sometimes
not. Maybe xdist?
|
|
|
|
|
|
|
| |
We used to search an OS-specific directory in addition to our own, specifically
so that Debian could use an OS-installed copy of jQuery and its plugins. But we
no longer have jQuery or any third-party JavaScript code, so we don't need to
search the Debian directories.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
That was for Python 2, which we don't support anymore.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now when a goldtest has a failure, the actual mismatched output will be written
to the tests/actual directory.
Along the way, I removed some obsolete settings which were only used by unittest
and unittest_mixins, which we no longer use:
- COVERAGE_KEEP_TMP
- COVERAGE_ENV_ID
- $TMPDIR/coverage_test
|
|
|
|
|
|
|
|
| |
Fixes a few unusual issues with reports:
- #580: HTML report generation fails on too long path
- #584: File collisions in coverage report html
- #1167: Remove leading underscore in coverage html
|
|
|
|
|
|
| |
This makes coverage warnings visible when running test suites under
pytest. But it also means some uninteresting warnings would show up in
our own test suite, so we had to catch or suppress those.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed were:
- StringIO
- configparser
- string_class
- unicode_class
- range
- zip_longest
- get_thread_id
- path_types
- shlex_quote
- reprlib
|
| |
|
|
|
|
| |
We don't need to use the one from unittest_mixins.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
One step of moving to pure pytest tests.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The tests were failing because of differences in file paths. It was
comparing:
C:\Users\runneradmin\AppData\...
to:
C:\Users\RUNNER~1\AppData\...
and failing. These changes normalize the file paths so the comparisons
work properly.
|
| |
|
|
|
|
|
|
|
|
| |
* Displaying timezone information in HTML report
* A helpber to format datetime with local timezone
* No backward compatibility with older python versions
|
|
|
|
|
|
| |
fix reporting of contexts when `relative_files = True`
fixes #900
|
| |
|