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

Simplify tests synchronization #133

Closed
andreasciamanna opened this issue Jun 5, 2020 · 3 comments
Closed

Simplify tests synchronization #133

andreasciamanna opened this issue Jun 5, 2020 · 3 comments
Labels
sync manual, draft tests and test automation synchronisation ui\ux ui \ ux development and defects
Milestone

Comments

@andreasciamanna
Copy link

I've testing Testomat with a suite of 250+ tests.

I'm now supposed to edit each test by adding a unique identifier, which is different for each test.

This is a bit cumbersome requirement which I believe could be fixed with some automation.

I suppose the reporter (I'm using Jest) would not be able to automatically edit the file, but maybe a different tool could be written so it can do that when running the tests.

Something similar to what happens when a snapshot fails to test and an option to update them is provided, but this one would update the test themselves.

In any case, in the current state which requires manual edit, I doubt I would ever dare to ask the developers to add these unique IDs in all existing tests or every time a new test is imported :)

Thanks.

@poliarush
Copy link
Collaborator

poliarush commented Jun 5, 2020

@andreasciamanna
In fact, no need to edit all tests. You need to be sure names are the same. That's all.

You can import all your tests as it's and execute them, it should be matched by test names.
No extra work should be done.

However, there may be a case where names are different in testomat.io and source but tests should be matched than ID should be used.

Anyway, we need to think about how to simplify that process.

@DavertMik
Copy link
Contributor

DavertMik commented Jun 5, 2020

Yes, just as @poliarush said - if you won't update test, you can leave things as they are.

But if you update a test, either rename it, or move it, you can append a Test ID into it for proper matching.

Anyway, there is no requirement to add ids manually to all tests. Reporter and tests uploading will work without it


P.S. But yes, we plan in future releases to do the code synchronization with making pull requests to your code. So you could automate this process

@andreasciamanna
Copy link
Author

andreasciamanna commented Jun 5, 2020

Sound good!

At the moment, looking at the imported tests, I see we could improve some descriptions and names, so I was tempted to change them from the web interface until I saw that warning.

But indeed, if I can change them from the web interface I can as well add the missing IDs in the code :)

Thanks!

@poliarush poliarush added sync manual, draft tests and test automation synchronisation ui\ux ui \ ux development and defects labels Jun 5, 2020
@poliarush poliarush added this to the arion milestone Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sync manual, draft tests and test automation synchronisation ui\ux ui \ ux development and defects
Projects
None yet
Development

No branches or pull requests

3 participants