Refactor tests to use shared FFTDimension and FFTArray objects

Open
#143 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

Start by locating the test functions that repeatedly define FFTDimension and FFTArray objects, then identify which configurations are common across the suite. Review how those objects are used before deciding which shared variables are safe. Done means common setup is reused, special-case tests retain their own objects, and the full test suite passes.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Currently, we usually define an FFTDimension and FFTArray object for each test function separately. This could be avoided by defining a set of global variables that can be shared by the majority of the tests and thus improve readability and decrease computational overhead. We could of course still define these objects for a single test if that test requires special properties.

Dominant language
Python
Stars
13
Forks
0
PR merge metrics
No merged PRs in 30d

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 QSTheory/fftarray

All issues in QSTheory/fftarray

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.