Evan Tseng [:evanxd] Reporter
	Description • 10 years ago

      No description provided.

	Evan Tseng [:evanxd] Reporter
	Comment 1 • 10 years ago

https://bugzilla.mozilla.org/show_bug.cgi?id=984572#c11 is why to have the test.

	Evan Tseng [:evanxd] Reporter
	Comment 2 • 10 years ago

Hi Kevin,

For the implementation of the test, we might have some unstable problems.
For example, the password of the google account might be changed by somebody, and the test depend on the google calendar service. How do we figure out these, or these are not problems?

Maybe, we could not need to log in the real google calendar. We could make a fake google log in page, then let Calendar app interact with the fake page for the testing purpose. This idea might work, but might be not easy.

How do you think about the above things?

	Kevin Grandon :kgrandon
	Comment 3 • 10 years ago

My preference would be to have some test that is capable of running offline, using a mock HTTP server, which will go through the same code paths as google. I'm not sure that we'd want to emulate the google UI, perhaps all it needs to do is to hit the callback with a mock oauth response.

I'm wondering if we could use the marionette server here in shared/: https://github.com/mozilla-b2g/gaia/blob/master/shared/test/integration/server.js

I'm also going to ni? on :gaye as I think he's thought about this a fair amount and may have some ideas.

	Evan Tseng [:evanxd] Reporter
	Comment 4 • 10 years ago

After we have clear idea to fix this, I will give it a shot.

	Gareth Aye [:gaye] (back from PTO)
	Comment 5 • 10 years ago

So after some thinking, I think we'd like tests that run online against all of the providers we're supporting. The first two should be Google and Yahoo!. These tests won't run on Travis/TBPL. They'll serve two purposes.

(1) Monitoring our compliance with supported providers
(2) Diagnostic tool for developers investigating bugs caused by unexpected caldav interactions and ical data

My preference would be for this code to live outside of gaia and instead depend on gaia via npm/submodule/subtree/whatever.

	Evan Tseng [:evanxd] Reporter
	Comment 6 • 10 years ago

cc Edware, he is the QA engineer in productivity team.

	Evan Tseng [:evanxd] Reporter
	Comment 7 • 10 years ago

Hi Gareth,

Agree, the purposes is very useful for us.

For the implementation of the test to log in Google account,
I think we could just create a new folder named "marionette_external_service" at https://github.com/mozilla-b2g/gaia/tree/master/apps/calendar/test, and add the test file there in Gaia repo.

The good points of doing this:
1. It is easier to implement then the outside of gaia solution because we don't need to rebuild a infrastructure of running marionette test.
2. It is easier to maintain because the test code live with the app code together.
3. We could reuse the test code, for example `lib/calendar.js`.

So the remaining problem is that where could we run the test? Setup a public server, or any other server already existed to run the test?

How do you think?

	Evan Tseng [:evanxd] Reporter
	Comment 8 • 10 years ago

Hi Gareth,
How do you think about Comment 7?

	Gareth Aye [:gaye] (back from PTO)
	Comment 9 • 10 years ago

Ok that sounds fine to me. Let's use apps/calendar/test/interop/<provider>/

	Evan Tseng [:evanxd] Reporter
	Comment 10 • 10 years ago

Thanks, Gareth.

	Evan Tseng [:evanxd] Reporter
	Comment 11 • 10 years ago

We should wait for Bug 1003788 is fixed, because we refine the switchToApp method there. All tests depend on that.

	Dylan Oliver [:doliver]
	Comment 12 • 10 years ago

[priority] --> tracking-b2g:+ conversion

	BMO Automation
	Comment 13 • 6 years ago

Firefox OS is not being worked on