Skip to content
This repository has been archived by the owner on Oct 4, 2023. It is now read-only.

Output of Ataru #16

Open
nanoparsec opened this issue Aug 11, 2014 · 4 comments
Open

Output of Ataru #16

nanoparsec opened this issue Aug 11, 2014 · 4 comments
Assignees
Milestone

Comments

@nanoparsec
Copy link
Member

The output of Ataru should provide information that helps the user to find the sample that is not working anymore.

@nanoparsec nanoparsec added this to the sprint 2 milestone Aug 11, 2014
@moonglum
Copy link

I would suggest to write down a sample output here. Just to get a feeling how it should work!

@nanoparsec nanoparsec modified the milestones: sprint 2, sprint 1 Aug 18, 2014
@nanoparsec
Copy link
Member Author

My idea of a better output:

Tested file: [name of md file]

[name of testmethod] ...... Status [passed]

[name of testmethod] ...... Status [failed]
[Code of broken Sample here]
[origin md filename, line(s)]

Anything else?

@nanoparsec nanoparsec self-assigned this Sep 1, 2014
@nanoparsec nanoparsec added this to the sprint 4 milestone Sep 1, 2014
@schultyy
Copy link

schultyy commented Sep 1, 2014

I like

@moonglum
Copy link

moonglum commented Sep 2, 2014

  • What exactly is [name of testmethod] here?
  • I really like the output of the broken sample + filename, lines.
  • What happens when you test more than one md file, how will the output look like?

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

No branches or pull requests

3 participants