Amber end-to-end browser tests (was Re: [amber-lang] How to contribute to Amber)

kilon alios wrote:

What you describe is normal behavior and common practice to me. There is
definitely a need to work on older releases when depending on older
libraries , I am coming from python and though Python 3 has been around
for almost 6 years now and still a lot of python coders use python 2.

Ah, yes, this python 2/3 long-time split-personality is a bit of mystery to me, but I am more or less just an observer.

Another question is that Pharo has jenkins and its tests to automate
testing of releases that can catch these kind of problems immediately,
can amber utilize something similar ?

Definitely. It uses travis to run its unit tests on each commit and pull request. These unit tests are run from the cli runner, though; so problem with actually running amber in a browser are not caught.

I felt in more occasions in the past already that having some end-to-end tests (running the test suite in browser as well in phantomjs?) may be beneficial.

Just it takes time and energy to write such thing.

Even saucelabs and testing on multiple real browsers could be used, if taken more seriously (I think they have some free plan for open-source)>

Herby

On Tue, Jul 1, 2014 at 1:00 PM, Herby Vojčík <[hidden email]
<mailto:[hidden email]>> wrote:



    kilon alios wrote:

        Yeap as always my lack of experience and my weakness of missing


    Lack of experience is something which is a constant in this field.
    It goes so fast (only biontechnology is faster, probably), that
    being inexperienced with x is just the way how it works. Just use it
    a while, and you're not inexprienced anymore.

    That lack of detail is true... Lots of web things now use semantic
    versioning (look up semver, it's also the name of package they
    (bower, npm) use), it is good to look at their patterns (~1.10.1,
    ^1.10.1, 1.10.x, 1.x.x, >=1.10.1, <1.11.0 etc.) so that they are no
    black magic anymore and you feel less lost.


        important details shows. I trust your judgement obviously you
        have the
        experience to back it up.

        Overall the installation of amber has been quite easy if I
        exclude this
        minor issue with jquery-ui minified.

        I tried also with my Ubuntu but I had issues with installing
        bower, so I


    Strange. Whatever.

        gave up. But I am fine with Win7, afterall my main platform is
        MacOS.


        On Tue, Jul 1, 2014 at 12:31 PM, Herby Vojčík <[hidden email]
        <mailto:[hidden email]>
        <mailto:[hidden email] <mailto:[hidden email]>>> wrote:

             As (nearly) always, problem is between the keyboard and the
        chair ;-).

             You told bower to install jquery#1.10x, not jquery#1.10.x, as I
             advised yesterday and what worked in your Mac. I bet it
        works nicely
             in Win7 as well (I work in it)>



             But since this is a practical problem, I would lean to
        creating two
             distributions of amber - the main one being more on the
        bleeding
             edge, having jquery & jquery-ui >=2.0.0, and one, named for
        example
             amber+jquery1, which would have its jquery&jquery-ui still at
             versions 1.x.x.


    I am more interested in this part, and how would Nico and others
    look at this idea. It would help things. Moving helios to bootstrap3
    and ambber to jquery2 only is also the way, but there are still
    people / packages who want to use jquery1, so I would not haste this
    transition.

             Herby


    --
    You received this message because you are subscribed to the Google
    Groups "amber-lang" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to amber-lang+unsubscribe@__googlegroups.com
    <mailto:[hidden email]>.
    For more options, visit https://groups.google.com/d/__optout
    <https://groups.google.com/d/optout>.


--
You received this message because you are subscribed to the Google
Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [hidden email]
<mailto:[hidden email]>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

kilon alios wrote:

I see well even with just this unit testing with jenkins is very good
start. Well I will keep this in mind for the distance future when I have

Just to dispel some misunderstanding: There is no need to use Jenkins as Travis is used, it's also a CI system, blended with github.

And unit tests are run in Travis, actually. Just not using browser-loaded Amber, but using compiled-to-node test runner usable from cli.

Maybe you got all this, I am just a bit confused from this paragraph...

good experience contributing to Amber. For now small steps :)

Looking forward... there is lots of issues to solve.

On Tue, Jul 1, 2014 at 1:16 PM, Herby Vojčík <[hidden email]

<mailto:[hidden email]>> wrote:



    Definitely. It uses travis to run its unit tests on each commit and
    pull request. These unit tests are run from the cli runner, though;
    so problem with actually running amber in a browser are not caught.

    I felt in more occasions in the past already that having some
    end-to-end tests (running the test suite in browser as well in
    phantomjs?) may be beneficial.

    Just it takes time and energy to write such thing.

    Even saucelabs and testing on multiple real browsers could be used,
    if taken more seriously (I think they have some free plan for
    open-source)>

    Herby

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.