Rewrite all E2E tests using the Ginkgo.
There are a lot of E2E tests that need to be rewritten, so we record the rewriting of E2E in this issue.
The PR and issue of the completed E2E can be associated and recorded.
cc @nic-chen @starsz @imjoey
Yeah. Much appreciated.
As far as I know, @nic-chen had finished part of them but hadn't created PR.
Thanks @Jaycean
I think we could list a todo list by module
Thanks @Jaycean
I think we could list a todo list by module
OK, I'll make the list by E2E test file name
I think we can add the name of the person who is rewriting the file after each todolist, so as to avoid repeated development.
such as
Hi @Jaycean, would you mind if I rewrite the route import test in the e2enew test suite :)
Hi @Jaycean, would you mind if I rewrite the
route import testin the e2enew test suite :)
Thank you very much. It has been allocated in to do list. You can @ me if you have any questions.
Hey @Jaycean, I have rewritten the test using ginkgo for the mentioned test suite. Now I am facing issues to test it locally before opening a PR. I am following the doc to set up the environment for the testing using docker-compose. It's failing, so opened issue #1581. It seems, for now, its better to go with installing the required dependencies locally. Pushing the changes soon :) Thank you
Hey @Jaycean, I have rewritten the test using ginkgo for the mentioned test suite. Now I am facing issues to test it locally before opening a PR. I am following the doc to set up the environment for the testing using docker-compose. It's failing, so opened issue #1581. It seems, for now, its better to go with installing the required dependencies locally. Pushing the changes soon :) Thank you
Thank you for your contribution. I have replied to you in issue. If you have more questions, you can ask them in issue.
Most helpful comment
I think we can add the name of the person who is rewriting the file after each todolist, so as to avoid repeated development.
such as