-
-
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
Add [twitter] tests #1394
Add [twitter] tests #1394
Conversation
inaccessable | 404 etc invalid user | no data returned from endpoint invalid | error thrown
Generated by 🚫 dangerJS |
38071f0
to
df166cd
Compare
5f886a1
to
03c233e
Compare
03c233e
to
d16a115
Compare
Full coverage except for when |
|
||
t.create('URL') | ||
.get('/url/https/shields.io.json') | ||
.expectJSON({ name: 'tweet', value: '' }); |
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 is a confusing badge URL!
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.
Yeah, Don't think it would be a very often used badge,
As it would need to be included as an <object>
for the link to actually work.
Otherwise its the same as using https://img.shields.io/:tweet--grey.svg?style=social&logo=twitter
Will be good once we can get #966 implemented to see how often certain badges are being used.
Add test for twitter,
Add error handling messages to right hand side of badge:
invalid
,inaccessible
,invalid user