Using externally stored data within tests

Open
#21 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cmake

Research direction

Start with test/cmake/app_datasources.cmake around line 57 and review how the external archive is currently handled. Compare that behavior with the example_data/1024 and example_data/64 layout; done means the archive can provide those nested bins and reads paths without hard-coded extraction steps.

Written by the indexing model from the issue text.

Description

I currently use an archive of the structure:

example_data/
├── 1024
│   ├── bins
│   └── reads
└── 64
    ├── bins
    └── reads

where the bins and reads directory contain 64 1024 files each, respectively.

It doesn't seem easily possible to extract that archive.tar.gz to provide, say, 1024/bins/... etc. in the data directory.
To do so, I need to hard-code the steps in the app_datasources.cmake https://github.com/seqan/app-template/blob/90659e3dacd4f7ae7c52149eb08517b822a38ad7/test/cmake/app_datasources.cmake#L57

Maybe there is a more elegant solution?

Dominant language
CMake
Stars
6
Forks
9
Avg merge
23h 34m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seqan/app-template

All issues in seqan/app-template

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.