Android integration tests and modules
by Summers Pittman
Ideally we would like to quit using the Robolectric Android stubs and
begin using Google's Android APIs for linking and testing. This is one
of the reasons that the unit tests havn't been brought over to the
modules YET. Over the weekend (between family duties and internet
issues) I did a lot of research and coding towards moving our tests into
the module packages. With the release of X86 emulators and stability
Genymotion, I think that using solely integration test projects for our
testing is now doable.
The Android SDK (current, ANT/Eclipse based) way is to have a separate
test project. The Android SDK (future Gradle based) way is to have your
tests in a test package. The maven way (Maven based Android builds) is
to have a parent project with two children: one child being code and the
other child being tests.
Currently we have one BIG integration test project which contains all of
our integration tests. I think that we should move the tests out of our
monolithic project and into the modules where they probably belong. I
also propose that we make each module in the two child project pattern
that then Maven based builds recommend. When it is time to move to
Gradle then we can just fiddle with sourceSets and kill the Maven build.
Wdyt?
--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
12 years, 1 month
News from iOS Modules front
by Corinne Krych
Hello Guys,
Last Tuesday during our (favourite) iOS meeting [1] [2] we talked about modularization. We agreed with Android team modularization is scheduled for 2.0.
For iOS we have several actions:
1. rename existing repos (too bad we don’t follow well Android convention)
• aerogear-ios-crypto
• aerogear-ios-push (thanks passos for the suggestion)
• aerogear-ios-otp
• aerogear-ios-xcode-template
• aerogear-ios-cookbook
Since we’re talking about renaming, what about dropping “arerogear” for the repo name? all those repos belong to aerogear organization anyway. Maybe removing the aerogear part will stress more the small libraries aspect. Maybe sth we already discussed but can’t remember/find it. wdyt?
2. Pipe and Store deprecated. All aerogear-ios we’ll stick to 1.7 version and will be marked deprecated.
But …. don’t be scared new modules will replace them:
• aerogear-ios-http : Lightweight lib around NSURLSession to ease HTTP calls with pluggable request and response Serializers. Very very Draft version [3] with some cookbook recipe [4]. With this module we will work directly with NSURLSession (iOS foundation networking) instead of using AFNetworking. Sure Andrea will like it: no dependency :)
• aerogear-ios-oauth2 : dependent on aerogear-ios-http, bring all the good stuff like AccountManager, OAuth2 extensible adapters, fluid http post/get ...
• aerogear-ios-storage usage of incrementalStorage to plug into Core Data
Those modules will be written in Swift code. We’ll test them both in iOS7 and iOS8.
3. Cookbook recipes rpo
• tag our repo 1.7: we didn’t have a tag strategy for cookbook demos but with the move from 1.X to 2.) I think we should
* Swift demo naming convention add “-swift” for Swift version like we did [5]. We should also append “-objc” to other recipes to be consistent.
4. Differentiate Swift vs Objective-C libs
How to differenctiate Swift code. Specially for aerogear-ios-push which will be declined in 2 versions? One suggestion from Matthias was to have 2 separate branches.
master -> objc-c
until iOS8 is released and stable.
I’m +1 with that idea.
Let me know if you have suggestions/objections. When we reach an agreement, I’ll create associated JIRA.
++
Corinne
[1] http://oksoclap.com/p/aerogear_ios_meeting_01072014
[2] http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...
[3] https://github.com/corinnekrych/aerogear-ios-http
[4] https://github.com/corinnekrych/Weather
[5] https://github.com/aerogear/aerogear-push-helloworld/tree/master/ios-swift
12 years, 1 month
aerogear-js lock library dependencies
by tolis emmanouilidis
Hi,
After taking a look at the PR [1] that Matthias made on AeroGear JS, I have
noticed that some of our library's dependencies have been changed. For
instance, the version of the Vert.x javascript client used in our
integration tests is 2.0.0.Final. However the new version is 2.1.2. The
same happens with the Eclipse Paho MQTT WS JavaScript Client. Its API has
been changed since Jan 29 so the AeroGear-JS notifier adapter needs to
comply with these changes.
I would suggest to lock the dependency versions and update our docs to
point these specific versions (at least for the cases where the
dependencies API is changed and AeroGear-JS code needs to be updated). Then
we can open JIRA(S) and start updating the code.
wdyt?
[1]: https://github.com/aerogear/aerogear-js/pull/141
12 years, 1 month
[UnifiedPush Server] Way to 1.0.0.Final
by Matthias Wessendorf
Hello team!
1.0.0.Beta2 is out and 1.0.0.Final is around the corner!
The list of open JIRAs is looking really good (see [1]). The most tickets
are around our quickstart demos and documentation. There are a few tickets
that require commits to the UPS itself. Gabriel did a review of the UX/UI
and filed three tickets (AGPUSH-934, AGPUSH-935 and AGPUSH-936) that he and
Lukas will be working on.
The release date for the 1.0.0.Final will be August 25th/26th and therefore
I propose to do a 'code freeze' for the UPS around the 19th or 20th August
to ensure its stability. However, in case something comes up (e.g. during
testing), I think only 'blocker' or 'critical' fixes should be allowed to
be merged during that time. Goal is to minimize risks!
Once the UPS 1.0.0.Final is out, there are a few 1.0.x release planed to
address things (if needed) and picking up new releases of our own
dependencies (e.g. Keycloak)
Any thoughts ?
Greetings, Matthias
[1]
https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTa...
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
12 years, 1 month
Cordova Push Plugin Release
by Erik Jan de Wit
Hi all,
After successful testing I’m happy to announce that the 0.7.0 version of the aerogear-pushplugin has been released. Thanks to everyone involved in making this release happen.
The new features bugs fixed are:
Bug
[AGCORDOVA-22] - android binaries installed for other platforms
Feature Request
[AGCORDOVA-23] - Support content title with gcm notifications on android
[AGCORDOVA-25] - iOS8 support for push registration
12 years, 1 month
