unused testing requirements by CI testing

[reactive-firewall]

History:

❓ is this used in CI ?

Originally posted by @reactive-firewall in #51 (comment)

Originally replied to by @reactive-firewall in #51 (comment)

---

Triage:

• So this needs to be triaged and tracked
• . . . and eventually resolved

---

Read issue's discussion for progress and latest status

[reactive-firewall]

🤔 Triage:

• This is an enhancement

• the goal is to have separate test requirements used by CI

  • regression testing is as simple as ignoring "test-requirements.txt" (as in what we do now)
  • this can be done with the common heuristic of the file "test-requirements.txt" (is there a PEP for this?)
  • and a minor refactor to CI configs to use "test-requirements.txt"
    should formalize the regression test but making the refactor a NEW test like extras

• 💡 also should make the requirements consistant across the multiple config files:

  • setup.*
  • project.toml thingy
  • test-requirements.txt (./tests/requirements.txt)
  • requirements.txt
  • tox.ini
  • CI configs
  • Makefile (not really needed)