calabash run should not expect there to be an 'android' or 'ios' profile

[jmoody]

I ran into this output:

$ be calabash run ../../spec/resources/android/xtc-android-sample.apk 
Could not find profile: 'android'

Defined profiles in cucumber.yml:
  * app
  * default
  * formatter
  * verbose

This is not a x-platform project.

Do I need to update my support/env.rb and support/hooks.rb? They were generated some time ago.

[TobiasRoikjer]

Yes this is expected behaviour. calabash run uses the profile android or ios

[jmoody]

This doesn't seem right. If the project is not x-platform, android or ios does not make sense.

Does calabash generate allow you to configure this?

[TobiasRoikjer]

@jmoody I consider this expected behaviour and not a bug. Have you changed your opinion?

[jmoody]

I don't think this is the correct behavior. Assigning to Karl for a decision.

[krukow]

I need more information to decide this. Let's discuss offline.

[krukow]

@jmoody @TobiasRoikjer ^

[TobiasRoikjer]

@jmoody If you generate skeletons using a newer version this is expected behaviour. You are right that this might be unexpected when you are targeting only one platform, but that means you have created your own hooks and env instead of basing them on the default generated ones.

A user can always just run using cucumber.

I am not certain this is the best approach, and I can be convinced to change this behaviour

[krukow]

@jmoody @TobiasRoikjer I don't think we should require profiles of specific names. What we should require is that certain configuration is called so that either iOS or Android is configured - does that make sense.

[TobiasRoikjer]

The run command is removed.