Giving the Android extension a name that sticks

[dan.j.allen]

As I was watching the Arquillian talk from JavaZone, one thing I picked up is the stark contrast between the extensions with custom names and those that just put Arquillian in front of generic name. I noticed this especially w/ the Android extension. Consider this list:

Arquillian Drone

               Warp

               Graphene

               Ape (persistence extension)

               Android

Arquillian Android just doesn't seem to fit. I think this is one area where Seam 3 really lost steam. Many of the modules were just concepts, like Seam Transactions, Seam Persistence, Seam REST, etc. However, the name Seam Catch was so...catchy, that it really stuck out...and rolled off the tongue.

Thus, I'd like to propose selecting a new name for Arquillian Android. The package names don't really concern me. We can start with the formal module name, then weave it down to the code as necessary.

Here are some candidate names I strung together:

Arquillian Cyborg (combination of organic and mechanical parts)

               Borg

               Andie (the Android mascot is sometimes referred to as Andy)

               Alienoid

               Hadaly (from novel that popularized the word "android")

               Rodroid

               Anbot

               Ash (from Aliens)

               Testdroid

               Eve (from WALL-E)

               Droidium (play on Android, Robotium and Delirium)

Though it's listed last, I really think "Droidium" is a winner. It probably best describes what the extension is doing atm, which is tapping into the *iums (Selenium and Robotium).

[aslak]

We do have iOS support in the pipeline as well.

Maybe a play on Mobile, or names that places Android and iOS on two sides of something, or the same side..

[kpiwko]

I'd like to eventually merge mobile extensions together, replacing our custom code with integration with upstream components. I'm currently thinking of integration with https://github.com/eing/moet, which was discussed on Java One.

[aslak]

aa yes. Remember you spoke about it

[dan.j.allen]

There's a video about moet from the mobile testing summit:

http://www.youtube.com/watch?v=JRuSOhsiBfc&feature=plcp

There's also a lot more videos covering some great raw material for mobile testing on that site:

http://www.youtube.com/MobileTestingSummit

I browsed moet briefly and while it looks pretty good, there might be some better stuff out there.

Anyway, I still think we need a cool name. I keep coming back to Droidium (even if we hit other devices, we tip our had to the open source platform )

[kpiwko]

I like Arquillian Eve, however Arquillian Droidium would definitely be easily to be searched for.

Droidium surprisingly fits Graphene theme as well http://spacequest.wikia.com/wiki/Droidium

[dan.j.allen]

Cool!

(Don't worry, we'll find a way to fit Eve into the story soon enough).

On a side note, we are also proposing calling the Arquillian Transaction extension "Neuralizer" (or "Neuralize"). Get it?

Btw, we won't necessarily impose the names on the packages, but we'll definitely use them for the story.=

[smikloso]

So there are basically three "extensions".

The first one is Arquillian Android container itself -> https://github.com/smiklosovic/arquillian-container-android

That should follow default Arquillian container naming (arquillian-{name of container}) as adapter dependency artifactId.

The second one is native extension -> https://github.com/smiklosovic/arquillian-container-android-drone-native,

I am ok with Arquillian Droidium so if I get it right, name of dependency to add to project pom.xml should be arquillian-droidium-(depchain?)

The third one is refactored web extension from Karel's arquillian-extension-android https://github.com/smiklosovic/arquillian-container-android-drone-web

I do not know what kind of name it should have ...

We could make native extension as "arquillian-droidium-native" and web testing extension as "arquillian-droidium-web". Are you ok with this?

Android container is made as pluggable, when you put native extension on class path, you are testing natively, when you put web extension on class path, you are testing web applications. So you have just one container and you just choose what way you are going to test.

[dan.j.allen]

Stefan,

I love the idea of using the qualifier to make the distinction between native and web. This way, we don't confuse people by introducing too many names, and it's very clear what purpose each extension serves. I think you nailed it!

For those following along, the proposal is:

• arquillian-container-android - the Arquillian Android container/connector
• arquillian-droidium-native - An extension for testing a native Android application
• arquillian-droidium-web - An extension for testing a web-based application from Android

+1

[dan.j.allen]

Btw, this set of extensions is huge! I'm so excited to see it get adopted.

[smikloso]

Yeah, it was my long term project in school  http://miklosovic.net/main.pdf

Just released book about Arquillian was very usefull as well! I think I am the first one who have cited it .

[aslak]

I would like Arquillian Droidium to be the common name for the Arquillian Android Extension. Then the extension contain the submodules like container, web, native, ++

[kpiwko]

Stefan,

can you please merge all your arquillian-container-android* repositories together so they share lifecycle? They will become Arquillian Droidium and would make former Arquillian Android Extension obsolete, both github and jira speaking.

Also, I think it would make sense to rename package to org.jboss.arquillian.droidium in such case.

Thanks,

Karel

[aslak]

I've added repository https://github.com/arquillian/arquillian-droidium

Could get a pull request that merge the container/web/native extensions into one coherent "Droidium" release there.

Owned/Administrated by the extesion-droidium team which currently consist of Karel, Lukas, and Stefan.

[smikloso]

Hi,

while I was renaming drone extension for native testing, I was going to rename packages to something like org.jboss.arquillian.droidium.native.api but JBDS denied to do so saying that "native" string is not a valid identifier for a package . It seems we are hitting Java specification details here ...

I think something like _native would be pretty ugly name for it. Let's have some mini poll here ... any ideas?