-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Split up [github] testers #2560
Conversation
|
@@ -42,7 +42,6 @@ module.exports = class GithubContributors extends LegacyService { | |||
message: '397', | |||
color: 'blue', | |||
}, | |||
keywords: ['GitHub', 'contributor'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More of a question as I'm not familiar with search, but does it do partial word matches? I.e. will contributor
still be matched in search since the title contains contributors
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
const t = (module.exports = require('../create-service-tester')()) | ||
|
||
t.create('hit counter') | ||
.get('/torvalds/linux/goto.json') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't related to the refactored tests in this PR but the GH Search hit counter badge isn't rendering for me in the staging deploy env. You mentioned in #1358 (comment) that perhaps it is just that particular repo that is slow, so would it be worth using a different repo for this test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, I think it would. Perhaps we should also update the example, which is what renders in the staging deploy.
One of the open issues PRs also tends to time out. I think it's the undefined label test. We could try it on a smaller repo or give it a longer timeout.
I try to avoid changing things while they're being moved because it's hard to compare what's changed, so let's handle this in a follow-on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! the tests are a lot easier to find now
create-service-tester
.Conflicts nominally with #2470. Let's merge that ASAP and this right afterward so as to unblock the rest of #2320.