Skip to content
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

Need Unit Tests, Bug Repros #17

Open
EvanBalster opened this issue Jan 19, 2018 · 0 comments
Open

Need Unit Tests, Bug Repros #17

EvanBalster opened this issue Jan 19, 2018 · 0 comments

Comments

@EvanBalster
Copy link
Owner

I'm seeking unit tests and bug reproductions from users.

Unit tests should be submitted here as JSON files containing one or more tiddlers. To ease automation, unit tests should follow this format:

  • Unit tests:

    • Tag with FormulaTest.
    • Text is a single formula construct (of any type) whose result should match:
      • The result of rendering the match field of the test tiddler, if present.
      • "TRUE" otherwise.
    • Name using a prefix scheme based on the test subject
      • Bugs: FormulaTest/Regression/<Test Name>
      • Functions: FormulaTest/Functions/<Function Name>/<Test Name>
        • Function names in ALL CAPS
      • Language: FormulaTest/Feature/<Feature Name>/<Test Name>
        • Feature names being things like "Let", "Function", "Closure", "Transclude"
      • Syntax & Compilation: FormulaTest/Compiler/<Feature Name>/<Test Name>
      • Miscellaneous Tests: FormulaTest/Misc/<Test Name>
  • Additional tiddlers used as data in unit tests:

    • Tag with FormulaTestData.
    • Prefix with the unit test's fully-prefixed name, with an additional slash and name.

Feel free to ask questions about this format or suggest changes or additions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant