Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
fslpy
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Analyze
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
FSL
fslpy
Commits
248e1a78
Commit
248e1a78
authored
6 years ago
by
Paul McCarthy
Browse files
Options
Downloads
Patches
Plain Diff
TEST: Nibabel/indexed_gzip updates broke some tests
parent
49dd588f
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tests/test_image.py
+14
-2
14 additions, 2 deletions
tests/test_image.py
with
14 additions
and
2 deletions
tests/test_image.py
+
14
−
2
View file @
248e1a78
...
...
@@ -30,6 +30,18 @@ from fsl.utils.tempdir import tempdir
from
.
import
make_random_image
from
.
import
make_dummy_file
try
:
from
unittest
import
mock
except
ImportError
:
import
mock
try
:
import
indexed_gzip
as
igzip
except
ImportError
:
igzip
=
mock
.
MagicMock
()
igzip
.
ZranError
=
mock
.
MagicMock
()
def
make_image
(
filename
=
None
,
imgtype
=
1
,
...
...
@@ -116,8 +128,8 @@ def test_load():
shouldRaise
=
[(
'
notexist
'
,
fslpath
.
PathError
),
(
'
notexist.nii.gz
'
,
fslpath
.
PathError
),
(
'
ambiguous
'
,
fslpath
.
PathError
),
(
'
notnifti
'
,
ImageFileError
),
(
'
notnifti.nii.gz
'
,
ImageFileError
)]
(
'
notnifti
'
,
(
ImageFileError
,
igzip
.
ZranError
)
),
(
'
notnifti.nii.gz
'
,
(
ImageFileError
,
igzip
.
ZranError
)
)]
with
tempdir
()
as
testdir
:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment