aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suman Karumuri (JIRA)" <>
Subject [jira] [Commented] (AURORA-451) Setup test infrastructure for the UI
Date Sat, 31 May 2014 07:25:01 GMT


Suman Karumuri commented on AURORA-451:

I have also investigated grunt, but decided not to use it since it didn't seem to provide
any additional advantages over writing gradle tasks our selves. Further, it would be an additional
wrapper to debug if something fails. This keeps things way simpler. 

More investigation is needed to see if protactor or karma is better for our use case. Protractor
is newer and is supposed to be operationally better when running in CI. However, I think we
should start with karma and see if it works in our CI since there is more documentation about
it out there. Protractor seems relatively new and the documentation about it is sparse. 

Also, please ensure that the source files in karma.conf.js are loaded in the right order.
Else, weird errors show up. 

> Setup test infrastructure for the UI
> ------------------------------------
>                 Key: AURORA-451
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>          Components: UI
>            Reporter: Suman Karumuri
>            Assignee: Suman Karumuri
> Create a basic infrastructure to run unit tests on the aurora UI. 
> The plan is to setup protractor[1] tests so it can run as part of gradle build using
the gradle grunt plugin[3][4][5]. [2] provides the best summary of protractor. 
> [1]
> [2]
> [3]
> [4]
> [5]

This message was sent by Atlassian JIRA

View raw message