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
People are very confused by the current processes for testing and generating implementation. It is unclear where results belong, there's outdated information spread across different repos, duplicate information, no clear reference.
Describe the overall process (independent from specific events) for all specifications
Describe where to put results
Describe where to find input templates
We should list the existing relevant issues and resources
How to generate the Implementation Report should be documented
Transparency on the process should be achieved via consistent descriptions and instructions
We should have open-source tools for all the tooling
Keep stable basis for testfests: Avoid renaming assertions / recreating templates during the testfest
The text was updated successfully, but these errors were encountered:
People are very confused by the current processes for testing and generating implementation. It is unclear where results belong, there's outdated information spread across different repos, duplicate information, no clear reference.
Describe the overall process (independent from specific events) for all specifications
Describe where to put results
Describe where to find input templates
We should list the existing relevant issues and resources
How to generate the Implementation Report should be documented
Transparency on the process should be achieved via consistent descriptions and instructions
We should have open-source tools for all the tooling
Keep stable basis for testfests: Avoid renaming assertions / recreating templates during the testfest
The text was updated successfully, but these errors were encountered: