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

Test order no longer maintained since 2.3.0 #850

Closed
JasonCust opened this issue May 13, 2015 · 3 comments
Closed

Test order no longer maintained since 2.3.0 #850

JasonCust opened this issue May 13, 2015 · 3 comments
Labels

Comments

@JasonCust
Copy link

I am not quite sure this is an issue but without documentation explicitly stating otherwise (at least that I could find) it could be a logical expectation that test declaration order would be maintained. It appears since 2.3.0 the declared order for tests is no longer preserved:

it('a', function (done) { console.log('a'); setTimeout(done, 100); });
it('b', function (done) { console.log('b'); setTimeout(done, 100); });
it('c', function (done) { console.log('c'); setTimeout(done, 100); });
it('d', function (done) { console.log('d'); setTimeout(done, 100); });
it('e', function (done) { console.log('e'); setTimeout(done, 100); });
it('f', function (done) { console.log('f'); setTimeout(done, 100); });
it('g', function (done) { console.log('g'); setTimeout(done, 100); });
it('h', function (done) { console.log('h'); setTimeout(done, 100); });
it('i', function (done) { console.log('i'); setTimeout(done, 100); });
it('j', function (done) { console.log('j'); setTimeout(done, 100); });
it('k', function (done) { console.log('k'); setTimeout(done, 100); });
it('l', function (done) { console.log('l'); setTimeout(done, 100); });
it('m', function (done) { console.log('m'); setTimeout(done, 100); });
it('n', function (done) { console.log('n'); setTimeout(done, 100); });
it('o', function (done) { console.log('o'); setTimeout(done, 100); });
it('p', function (done) { console.log('p'); setTimeout(done, 100); });
it('q', function (done) { console.log('q'); setTimeout(done, 100); });
it('r', function (done) { console.log('r'); setTimeout(done, 100); });
it('s', function (done) { console.log('s'); setTimeout(done, 100); });
it('t', function (done) { console.log('t'); setTimeout(done, 100); });
it('u', function (done) { console.log('u'); setTimeout(done, 100); });
it('v', function (done) { console.log('v'); setTimeout(done, 100); });
it('w', function (done) { console.log('w'); setTimeout(done, 100); });
it('x', function (done) { console.log('x'); setTimeout(done, 100); });
it('y', function (done) { console.log('y'); setTimeout(done, 100); });
it('z', function (done) { console.log('z'); setTimeout(done, 100); });

// 2.1.0: a b c d e f g h i l k l m n o p q r s t u v w x y z
// 2.2.0: a b c d e f g h i l k l m n o p q r s t u v w x y z
// 2.3.0: a z c d e f g h i j k l m b o p q r s t u v w x y n
// 2.3.1: a z c d e f g h i j k l m b o p q r s t u v w x y n
@slackersoft
Copy link
Member

This is definitely not intended functionality. I'm not entirely sure what is causing the order to get mixed up, especially in such a consistent manner.

I'll take a look and see if I can get a fix together.

@JasonCust
Copy link
Author

Thanks @slackersoft!

@JasonCust
Copy link
Author

@slackersoft Any idea when this will be published to npm?

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

No branches or pull requests

2 participants