-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[refactor] tests #1983
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
Comments
Yes, I definitely agree with this plan.
|
Structure is done. Unfreeze merge for any branches. /cc @hiroppy need rebase next |
We don't rebase because a base branch will be broken if we force push. So I've always used cherry-pick. What do you think? (also, It depends on the committer to merge, but if the committer is not myself, then the commit revision is changed.) If you want to rebase next branch, I can fix. |
Yes, we need rebase 👍 |
ok, so maybe pr will be broken(because of rebasing base branch) |
And I deleted branch rules because if we set branch rules, we can not force push. |
👍 |
We completed migrating to the new directory structure. I'll close. |
No issue template. Ref: #1982 (comment)
Test structure (approximately):
Test naming:
MyClass.js
->MyClass.test.js
defaultPort.js
->defaultPort.test.js
server
directory and have namecompress-option.test.js
client
directory and have namesockPath-options.test.js
Next we should improve test performance, many tests are very long and written in effective way.
Some of tests files should be merge in other, some of separated based on above structure.
I am WIP on this after merge this PR
Ideally each option should have:
We should concentrate on
1
and2
points right now.Other changes what we should do:
--runInBand
it is decrease time on testsThe text was updated successfully, but these errors were encountered: