You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently don't test all types in the SDK, so when something doesn't work, we don't necessarily know where the issue resides. For instance we didn't know Enum didn't work until recently.
We should have a big Sway contract that uses all types and just test the whole contract as part of the harness.
The text was updated successfully, but these errors were encountered:
Currently, we have tests and test_project that cover a lot of cases. For example, we have several test_projects for enums: enum_as_input, enum_encoding, enum_inside_struct, nested_enums, struct_inside_enum.
How would we approach this issue? Do we make a new big test_project with all the types and repeat some tests?
How do we deal with the variations (struct in enum, tuple in enum, enum in tuple etc)?
I would propose that we leave the current tests as they are and add the ones that we think are missing.
I would also propose that we refactor the current test_projects. I would propose we use one for every custom type.
For example, put everything related to enums in one test_project but separate the different aspects with functions inside the contract and tests in the harness.
We currently don't test all types in the SDK, so when something doesn't work, we don't necessarily know where the issue resides. For instance we didn't know
Enum
didn't work until recently.We should have a big
Sway
contract that uses all types and just test the whole contract as part of the harness.The text was updated successfully, but these errors were encountered: