This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
1 / 11
Mar 2015

Some of us are in favor of switching to io.js28

Appium is already io.js compatible and we would make sure tests pass and all that.

Would switching from Node.js to io.js be an issue for anybody? I'm asking here in case our users have specific company requirements that would make this move impossible.

  • created

    Mar '15
  • last reply

    Mar '15
  • 10

    replies

  • 1.8k

    views

  • 6

    users

  • 3

    likes

  • 2

    links

pinned Mar 4, '15

unpinned Mar 4, '15

pinned globally Mar 4, '15

@Hassan_Radi If you were to switch, you'd have to change exe path to iojs.exe, but everything else would stay the same.

Hi @jonahss,

We have been using Appium for past 5 months and its a great tool.
But there are few issues which keep coming when executing tests through Appium, like
1. unknown server side error occurred
2. file not found exception,..., window dump hierarchy
3. chromedriver exited unexpectedly

With the move to io.js, will these issues be addressed ?
Could you also elaborate if this change means any significant difference in the way we use Appium, hope this question does not appear quite naive

Thanks,
Sujata

With my test automation tools I value stability and consistency highest. Nothing is more frustrating when a new version of some dependency or the tool itself is released and it causes problems with things that were working acceptably before.

The io.js weekly release schedule seems great if you're wanting to get bug fixes and new features, scary if every week some potential regression / breakage / deprecation is going to occur.

12 days later

unpinned Mar 20, '15