Skip to content

Conversation

@tkaye407
Copy link
Contributor

Added in a few quick fixes for alphabetizing the export lists. Furthermore, not sure if we should test to make sure it works properly in react native

@tkaye407 tkaye407 requested a review from adamchel February 14, 2019 21:35
Copy link
Contributor

@adamchel adamchel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work! Had a couple nits, but otherwise this looks great!

} from "mongodb-stitch-core-sdk";

/** @hidden */
export default class JestEventSourceEventStream extends BaseEventStream<JestEventSourceEventStream> {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[broader discussion] So this works and I know it's what I told you to do, but now this means that the Transports we wrote are not covered at all by our tests unless we do E2E browser, Node.js, and React Native testing.

We aren't going to make changes to the other transports again for a while probably, but it might be a good idea to file a backlog ticket to do some very rudimentary E2E smoke testing with an actual node server, actual react native app, and actual browser (via something like selenium) to make sure the transports properly interact with the network.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thoughts @jsflax ?

Copy link
Contributor

@jsflax jsflax Feb 14, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Considering how core of an element the transports are, I think we should add some basic tests to make sure everything still works, before merging this. More can be added later.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The point is that these transports can't be tested in Jest, so we'd have to create an entire E2E testing strategy, which I feel is out of scope for this ticket, which was meant to fix a bug.

Tyler did do some manual E2E in the browser to make sure the transports still work, and I think it would be good to merge if he did the same for Server and RN

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, fair point. That works for me.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 77.492% when pulling 44dde8c on tkaye407:cross-fetch into 05e0548 on mongodb:master.

@tkaye407 tkaye407 merged commit 2d311bb into mongodb:master Feb 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants