-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pytest - step 1 #553
Add pytest - step 1 #553
Conversation
This is mostly a refactor PR. I believe the first two points related to pytest can be delayed for another PR. Question: why does the testing framework even care about |
|
Is it possible to just exclude the directories which shouldn't contain tests? The link you gave suggests it's possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice test simplification, I think that #200 can be linked.
What is the problem with test_retirement
?
Co-authored-by: piotro888 <[email protected]>
It is possible, but not useful in our case, because
|
We try to control signal value before start of simulation: def test_rand(self):
self.retc = RetirementTestCircuit(self.gen_params)
yield from self.retc.mock_fetch_stall.enable() # To be fixed
with self.run_simulation(self.retc) as sim:
... |
This code doesn't make any sense. We missed it in #523. |
Hi,
here is a PR which is a first step towards using pytest as described in #405. In this PR:
a basic configuration for pytest is addeda new dependecy to requirements is addedRepl
RoundRobin
from amaranth to transactron, according to the recomendation from amaranthSimpleTestCircuit
added exception forTestbenchIO
naming which breaks test naming conventionadded exception for deprecation warnings related withRecord
There is a one warning left, but it should be fixed under separate PR, because it hides some error in
test_retirement.py
and it has to be investigated deeper.