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

Multi-aspect flexible tests #14

Open
jfgigand opened this issue Sep 7, 2016 · 2 comments
Open

Multi-aspect flexible tests #14

jfgigand opened this issue Sep 7, 2016 · 2 comments

Comments

@jfgigand
Copy link
Contributor

jfgigand commented Sep 7, 2016

Hi,

geocoder-tester takes a "Manichaean" approach, where each test address will either pass or fail, while the possibility to select specific test files and directories provides a good degree of test perimeter.

The question here is about test depth:

  • is it possible to test the geo coordinates only and not the address components?
  • is it possible to have custom expected properties which may be checked or not, depending on some runtime parameter?

More generally, what do you think about having different levels of testing that can be specified at runtime?

@yohanboniface
Copy link
Member

Why not.
An optional --fields=name,xxx may allow to run with only checking those fields.
The tricky part may be to tweak the test collector to only consider the good tests (and then of course only checking those fields when actually running them).

@jfgigand
Copy link
Contributor Author

jfgigand commented Sep 7, 2016

Yes, this looks like a good idea.
I should think more about the kind of testing we need in the long run, before choosing the approach.
Will keep you posted...

antoine-de added a commit to antoine-de/geocoder-tester that referenced this issue Jun 12, 2018
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