Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Organise demultiplex tests and fixtures around only 7 flow cell cases #2842

Closed
2 tasks
diitaz93 opened this issue Jan 15, 2024 · 3 comments
Closed
2 tasks
Assignees

Comments

@diitaz93
Copy link
Contributor

diitaz93 commented Jan 15, 2024

Description

In the context of demultiplexing, I have identified 7 different Illumina flow cell cases that share many characteristics:

  • HiSeqX single index
  • HiSeqX double index
  • HiSeq2500 double index
  • HiSeq2500 custom index
  • NovaSeq6000 pre 1.56 kits
  • NovaSeq6000 post 1.5 kits
  • NovaSeqX

The idea is that the demultiplexing test suite is designed around these 7 cases. For this, I chose one example from each group and added the flow cell directory data to the folder tests/fixtures/apps/demultiplexing/flow_cells in #2736. However, many tests and fixtures still use elements spread around the test directory from different flow cells in a disorganised way.

Suggested solution

With the help of fixture plugins introduced in #2816, create an organised set of fixtures that replaces old ones pointing to inconsistent flow cells with correct fixtures pointing to one of the 7 case flow cells.

PRs:

Pending tasks:

  • Remove all fixtures referring to other flow cells
  • Remove fixtures named CorrectSampleSheet.csv as all sample sheets in the flow cell folders should be correct, ill-shaped sample sheets should be in the broken_flow_cells fixture directory

This can be closed when

The demultiplexing testing suite is designed around the 7 flow cell cases.

Blocked by

N/A

@diitaz93 diitaz93 self-assigned this Jan 15, 2024
diitaz93 added a commit that referenced this issue Jan 16, 2024
This is the first step of #2842. Refactor the fixtures returning lists of `FlowCellSample` to only use elements from the 7 canonical flow cells in demultiplexing


### Added

- Raw sample file `tests/fixtures/apps/demultiplexing/flow_cells/190927_A00689_0069_BHLYWYDSXX/HLYWYDSXX_bcl2fastq_raw.json`  with anonymised names and projects

### Changed

- Renamed `novaseq_6000_pre_1_5_kits_lims_samples` and `novaseq_6000_post_1_5_kits_lims_samples` to explicitly include the bcl converter in their name

### Fixed

- Removed fixture `lims_novaseq_6000_bcl2fastq_samples`, replaced usages with `novaseq_6000_pre_1_5_kits_bcl2fastq_lims_samples`.
- Removed fixture `lims_novaseq_bcl_convert_samples`, replaced usages with `novaseq_x_lims_samples`
- Removed paths to lims sample files that were used only once. Instantiated Path in the fixture where they were used instead.
diitaz93 added a commit that referenced this issue Jan 16, 2024
…)(patch)

## Description
Part of #2842. First attempt to leave only fixtures of only 7 flow cells. Removed and renamed flow cell fixtures and their files. PR was growing too much so decided to stop this one here and continue in another PR.

### Added

- Directory `flow_cells_broken` to distinguish the files from  working flow cells from flow cells missing files (required by some tests)

### Changed

- Renamed several fixtures

### Fixed

- Removed fixtures and files for flow cells 180522_A00689_0200_BHLCKNCCXY and 170407_A00689_0209_BHHKVCALXX
@diitaz93 diitaz93 added the Test coverage Untested functions label Mar 19, 2024
@henrikstranneheim
Copy link
Contributor

@diitaz93 Done?

@diitaz93
Copy link
Contributor Author

@diitaz93 Done?

@henrikstranneheim Not yet, there is still a lot of debris from old fixtures that unfortunately are still used in some tests. A further cleaning is needed. I want to do this this summer if I have time but this is low prio

@diitaz93
Copy link
Contributor Author

diitaz93 commented Sep 3, 2024

Very low prio, not keeping as an issue

@diitaz93 diitaz93 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants