-
Notifications
You must be signed in to change notification settings - Fork 111
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
feat(specs): EOF: eof_test
generates state tests, and execute
in live devnets
#783
Conversation
51b8181
to
ed6f750
Compare
5d28f2f
to
c13e837
Compare
eof_test
generates state testseof_test
generates state tests, and execute
in live devnets
8fa0190
to
b49c253
Compare
7dbed0f
to
b0e189d
Compare
c066fe7
to
c22bea9
Compare
c22bea9
to
005acab
Compare
f47fef2
to
0334a20
Compare
3bec40e
to
5e989aa
Compare
0334a20
to
b2d3265
Compare
5e989aa
to
b4f6859
Compare
9b68305
to
193b29c
Compare
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.
Framework changes LGTM!
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.
LGTM, just one call for expanding the docs a bit
LGTM, modulo piotr's remark. |
193b29c
to
f33221f
Compare
fix(specs): Reuse same initcontainer as deploy code for state tests gen from eof tests fix(specs): Add docstrings for all `EOFTest` and `EOFStateTest` fields fix(specs): docstring
fix(tests): Single tests where the deployed container could not be infered
f33221f
to
fc6e701
Compare
I changed the approach of the state tests generated for init-containers, and trying to infer the deployed container from the sections worked reasonably well, with just a single test that needed to be updated by setting its I've updated the method to be the default and will proceed to merge. |
container-type section will be used. An error will be raised if the deployed container | ||
cannot be inferred. | ||
|
||
If the value is set to `None`, it is assumed that the container is invalid and the test will |
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.
is this actually accurate? not sth like:
If the value is set to
None
, it is assumed that the init container will fail to deploy, despite being valid EOF, and the test will expect that no contract is created.
?
🗒️ Description
REQUIRES #1220Merged-
eof_test
produces state tests (and blockchain tests)Create a state test out of an
eof_test
by:- State test generated from EOF tests have extra markers
All state tests generated automatically from the
eof_test
spec now have a different test ID, along with an extra marker applied.The test ID will show
state_test_from_eof_test
instead of simplystate_test
, e.g.:test_swapn_on_max_stack[fork_Osaka-state_test_from_eof_test-swapn_operand_0]
intead of:
test_swapn_on_max_stack[fork_Osaka-state_test-swapn_operand_0]
Also, all tests will have the extra markers
state_test_from_eof_test
orblockchain_test_from_eof_test
orblockchain_test_engine_from_eof_test
in order to be able to fill only these specific tests.E.g. using
-m state_test
will select all tests, includingstate_test_from_eof_test
tests:But using
-m state_test_from_eof_test
will only select state tests that have been automatically generated from an EOF test:Using
-m eof_test
will still produce the exact same tests as before.-
eof_test
executable in live networksThis change allows the
uv run execute
command to send EOF initcode transactions to live networks by using the same methodology described in the previous section.The marker
transaction_post_from_eof_test
will in this case send only EOF container validation tests to the live network:🔗 Related Issues
✅ Checklist
mkdocs serve
locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.