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
It would be really nice if this automatically got run against every known, compliant promises/A+ implementation every time it was updated so that:
a) authors wouldn't need to re-run tests even if they haven't changed anything
b) we'd know that authors weren't just telling people they were promises/A+ compliant without running this test suite.
The text was updated successfully, but these errors were encountered:
This is a great idea. The specifics might be tricky---e.g. if a library fixes itself, who's responsible for re-running the Travis build? I wonder if Travis has an API?
Travis does have an API, but I don't think it lets you re-build someone else's repo. If we gave all the implementers commit access to said repo then we could just let them add a new line with a comment to a 'history.md' file and cause it to build?
It would be really nice if this automatically got run against every known, compliant promises/A+ implementation every time it was updated so that:
a) authors wouldn't need to re-run tests even if they haven't changed anything
b) we'd know that authors weren't just telling people they were promises/A+ compliant without running this test suite.
The text was updated successfully, but these errors were encountered: