Skip to content

Commit

Permalink
Minor tidy, maintain order of parameterisation across tests.
Browse files Browse the repository at this point in the history
  • Loading branch information
JoeZiminski committed Jul 8, 2024
1 parent 5e11c4e commit 3ebd3b5
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/spikeinterface/core/tests/test_time_handling.py
Original file line number Diff line number Diff line change
Expand Up @@ -123,8 +123,8 @@ def test_times_propagated_to_save_folder(self, request, fixture_name, mode, tmp_
self._check_times_match(recording_cache, all_times)
self._check_times_match(recording_load, all_times)

@pytest.mark.parametrize("fixture_name", ["time_vector_recording", "t_start_recording"])
@pytest.mark.parametrize("sharedmem", [True, False])
@pytest.mark.parametrize("fixture_name", ["time_vector_recording", "t_start_recording"])
def test_times_propagated_to_save_memory(self, request, fixture_name, sharedmem):
"""
Test t_start and time_vector are propagated to recording saved into memory.
Expand Down Expand Up @@ -191,9 +191,9 @@ def test_time_sample_converters(self, request, fixture_name):
@pytest.mark.parametrize("bounds", ["start", "middle", "end"])
def test_slice_recording(self, time_type, bounds):
"""
Test after `frame_slice` and `time_slice` a recording or
sorting (for `frame_slice`), the recording times are
correct with respect to the set `t_start` or `time_vector`.
Test times are correct after applying `frame_slice` or `time_slice`
to a recording or sorting (for `frame_slice`). The the recording times
should be correct with respect to the set `t_start` or `time_vector`.
"""
raw_recording = generate_recording(num_channels=4, durations=[10])

Expand Down

0 comments on commit 3ebd3b5

Please sign in to comment.