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

Is this known feature or a bug? #37

Closed
sainianubhav opened this issue Oct 9, 2018 · 2 comments
Closed

Is this known feature or a bug? #37

sainianubhav opened this issue Oct 9, 2018 · 2 comments

Comments

@sainianubhav
Copy link
Contributor

I can invoke tests npm run nemo -- -G '#phone #add #US' and it runs two tests only for US.

I can invoke tests npm run nemo -- -G '#phone #add #US #HOME' and it runs just one test only for US and HOME.


['AU', 'BR', 'ES', 'FR', 'GB', 'GB', 'IN', 'MX', 'US'].forEach(CC => {
	['HOME', 'WORK'].forEach(t => {
		describe(`#phone #add #${CC} #${t}`, function () {
			it(`should test adding of phone of a specific type`, async function () {
				await add.default(this.nemo, phoneInfo.types[CC][t], CC);
			});
		});
	});
});

I want to know if A) This is a known feature and that it will stay. B) If its a bug and tests shouldn't be written like it.

I think when nemo goes to build metadata about tests, it somehow parses all the specs and just don't run them. Is that so? It runs later, after reading command line arguments.

@grawk
Copy link
Member

grawk commented Oct 11, 2018

The behavior seems correct based on the code. What is the expected behavior?

@sainianubhav
Copy link
Contributor Author

This is a feature then.

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

No branches or pull requests

2 participants