Skip to content
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

Fixed broken test suite #23

Merged
merged 6 commits into from
Oct 23, 2014
Merged

Fixed broken test suite #23

merged 6 commits into from
Oct 23, 2014

Conversation

jwngr
Copy link

@jwngr jwngr commented Oct 22, 2014

@mimming - Due to the recent POODLE security vulnerability, Firebase dropped support for SSL v3. Unfortunately, PhantomJS uses SSLv3 so this test suite was broken. Thankfully, Travis supports running the test suite in Firefox. Locally, the tests will be run in Chrome.

@jwngr
Copy link
Author

jwngr commented Oct 22, 2014

Things still aren't running properly on Travis. Please don't merge yet.

@mimming
Copy link
Contributor

mimming commented Oct 22, 2014

ack :) I'll wait for them to pass before I merge

On Wed, Oct 22, 2014 at 3:47 PM, Jacob Wenger notifications@github.com
wrote:

Things still aren't running properly on Travis. Please don't merge yet.


Reply to this email directly or view it on GitHub
#23 (comment).

This fixed an issue running the test suite in Firefox
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling b4909cc on jw-tests into * on master*.

@jwngr
Copy link
Author

jwngr commented Oct 23, 2014

WOOOOOOOOOOT! Got it working!

@mimming
Copy link
Contributor

mimming commented Oct 23, 2014

yay!

On Wed, Oct 22, 2014 at 10:57 PM, Jacob Wenger notifications@github.com
wrote:

WOOOOOOOOOOT! Got it working!


Reply to this email directly or view it on GitHub
#23 (comment).

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 86d9262 on jw-tests into * on master*.

@jwngr
Copy link
Author

jwngr commented Oct 23, 2014

Feel free to merge this in if you are happy with it. I've got a lot more repos to update with this new system...

@@ -21,7 +18,7 @@ var invalidBindVars = ["", 1, true, false, [], {}, [1, 2], {a: 1}, null, undefin
/* Helper function which runs before each Jasmine test has started */
function beforeEachHelper(done) {
// Create a new firebase ref with a new context
firebaseRef = new Firebase(demoFirebaseUrl, Firebase.Context());
firebaseRef = new Firebase("https://tests.firebaseio.com", Firebase.Context());
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this a special Firebase? or just a normal one that we own?

Copy link
Author

Choose a reason for hiding this comment

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

It's just a Firebase that Rob owns that we use in a lot of test suites. It's set to read true/write true and has no important data in it. I switched it from a demo Firebase because the Firebase client was having issues connecting to the demo Firebase for some reason. I'm going to work with Rob today to figure out why that was the case with firebaseio-demo.

Choose a reason for hiding this comment

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

Demo has been fixed - it had some mitigation for POODLE that was causing issues with Firefox

mimming added a commit that referenced this pull request Oct 23, 2014
@mimming mimming merged commit c13e4aa into master Oct 23, 2014
@jwngr jwngr deleted the jw-tests branch October 23, 2014 16:26
@FirebaseExtended FirebaseExtended locked and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants