Better E2E framwork for testing Testacular

[bitwiseman]

We need to verify output for reporters in e2e scenarios, but the current framework does not support it.

[vojtajina]

I hope I understand you correctly. You meant we need a better way of e2e testing Testacular itself. Basically the stuff that lives in test/e2e/, right ? (I renamed the issue)

We already discussed this with @dignifiedquire. Once we get the docs and stable release out, we should do this. I totally agree on this.

[vojtajina]

Some ideas for e2e - add more guys...

• syntax error and recovering after syntax error
• 3x kill & restart browser if does not capture in given timeout
• test testacular run functionality
• batching changes (multiple file changes within interval should trigger only one run)

[dignifiedquire]

It has begun. Progress can be seen here Dignifiedquire/testacular/e2e

[bitwiseman]

Very cool.
We'll be able to add checks for the contents of files (such as the junit reporter output) as well, via steps, right?

[dignifiedquire]

Yes, there will be steps to check for the existence and contents of a file.

[vojtajina]

Super awesome. Will send more feedback.

On Sun, Mar 17, 2013 at 12:52 PM, Friedel Ziegelmayer <
notifications@github.com> wrote:

Yes, there will be steps to check for the existence and contents of a file.

—
Reply to this email directly or view it on GitHubhttps://github.com/testacular/testacular/issues/325#issuecomment-15029448
.

[dignifiedquire]

Resolved in #684