Design Doc — New Testing Architecture implementation #1370
kasperski95
started this conversation in
Ideas
Replies: 2 comments 6 replies
-
This roughly makes sense to me, and conforms to what we discussed, although i have some questions:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Good job, I think it represents the idea, issues I see for now are:
|
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem
The New Protostar Testing Architecture has inherited design flaws, including ambiguous naming conventions and questionable code division. To prevent cyclical dependencies, proper code division is crucial. One specific issue is the concept of
Cheaters
, which manage part of the state and provide access to standard StarkNet functionality. Additionally, the termCheatcode
has lost its significance. Ambiguous naming also affects the documentation.Proposal
Legend:
Each subtitle defines an Object Stereotype.
https://khalilstemmler.com/articles/object-oriented/design/object-stereotypes/
Some less important connections are skipped on the diagram to favor clarity.
Unknowns
Will the Data Transformation logic be reimplemented in Rust?
Beta Was this translation helpful? Give feedback.
All reactions