Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
M
modelgen
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Taddeüs Kroes
modelgen
Commits
1b904eb1
Commit
1b904eb1
authored
Jul 11, 2012
by
Taddeüs Kroes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Moved code coverage configuration into .coveragerc file.
parent
9e8cbbdc
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
18 additions
and
10 deletions
+18
-10
.coveragerc
.coveragerc
+9
-0
Makefile
Makefile
+9
-10
No files found.
.coveragerc
0 → 100644
View file @
1b904eb1
[run]
branch = true
omit =
/usr/share/pyshared/*
test.py
tests/*
[html]
directory = coverage
Makefile
View file @
1b904eb1
TEST
:=
test.py
TEST
:=
test.py
COVERAGE_DIR
:=
coverage
COVERAGE_DIR
:=
coverage
COVERAGE_OMIT
=
/usr/share/pyshared/
*
,test.py,tests/
*
test
:
test
:
@
pyrg
$(TEST)
@
pyrg
$(TEST)
coverage
:
coverage
:
covclean
coverage erase
@
if
[
-d
$(COVERAGE_DIR)
]
;
then
rm
-rf
$(COVERAGE_DIR)
/
*
\
else
mkdir
$(COVERAGE_DIR)
;
fi
coverage run test.py
coverage run test.py
coverage
html
--omit
=
$(COVERAGE_OMIT)
-d
$(COVERAGE_DIR)
coverage
report
coverage
report
--omit
=
$(COVERAGE_OMIT)
coverage
html
clean
:
c
ovc
lean
:
coverage erase
coverage erase
rm
-rf
$(COVERAGE_DIR)
`
find
-name
\*
.pyc
`
rm
-rf
$(COVERAGE_DIR)
clean
:
covclean
rm
`
find
-name
\*
.pyc
`
.PHONY
:
test clean coverage
.PHONY
:
test clean coverage
covclean
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment