Unit test Fifo

Open Beginner friendly
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start with src/utility/fifo.py to understand pop_one(), to_list(), and extend(), then read the existing tests in test/utility/test_fifo.py. Run the FIFO test file before and after your changes. Done means these three methods have focused unit tests covering their expected behavior.

Written by the indexing model from the issue text.

Description

good first issue Maintenance

Under src/utility/fifo.py the Fifo class needs to be better unit tested (current unit tests can be found in test/utility/fifo.py.

At the moment push() and pop() are unit tested, so pop_one(), to_list(), and extend() need to be tested.

Dominant language
Svelte
Stars
4
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 neuralbertatech/natKit

All issues in neuralbertatech/natKit

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.