Some framework tests require tomopy

Open
#565 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

Start by locating the four named tests: test_pipeline_build_duplicate_id, test_pipeline_build_cpu_pipeline, test_build_pipeline_with_param_sweeps, and its duplicate listing. Trace why these UI-layer tests require tomopy and how they are included in the framework-test classification. Done means either the framework tests no longer require tomopy or the UI tests are consistently excluded from that classification.

Written by the indexing model from the issue text.

Description

testing

In work on trying to reduce the usage of conda packages in httomo installation (#564) it was discovered that there are four UI layer tests that are part of what is currently classified as "framework" tests, that require tomopy to be installed to be able to run:

test_pipeline_build_duplicate_id
test_pipeline_build_cpu_pipeline
test_build_pipeline_with_param_sweeps
test_build_pipeline_with_param_sweeps

It may be worth either:

  • trying to remove the dependency on tomopy in framework tests
  • or, rethink the classification of what is part of the framework and what isn't (ie, the UI layer is one of the outermost layers of httomo, it could therefore be argued that it's not part of the core framework, and thus it may be fine for the UI layer to depend on tomopy - but in this case, it may then make sense to exclude the UI layer tests from the "framework" tests)
Dominant language
Python
Stars
10
Forks
5
Avg merge
5d 17h
Merged PRs (30d)
1

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 DiamondLightSource/httomo

All issues in DiamondLightSource/httomo

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.