[openstack-dev] [Horizon] On testing...

Hi all, > 2. We don't have enough higher-level (integration leve) test coverage for our newer angular interfaces. I previously wrote about new horizon integration autotests architecture and parallel mode: https://github.com/sergeychipiga/horizon_autotests. In this automated scope there are many

[openstack-dev] [Horizon] On testing...

Hello, all! > Also there is > > 5. Parallelize integration tests. > Talking about parallel launching of horizon integration tests. Right now I have migrated horizon autotests to new architecture: https://github.com/sergeychipiga/horizon_autotests, which uses pytest to run tests. I launch my

Re: [openstack-dev] [Horizon] On testing...

Another option is to just run separate test jobs. Like Django tests in one runner, and angular in another. As different panels are deprecated and removed, and we alter the scope of the tests, two jobs might act as a good stopgap. Rob On 21 July 2016 at 01:58, Richard Jones

Re: [openstack-dev] [Horizon] On testing...

On 21 July 2016 at 10:13, Timur Sufiev wrote: > I'm not sure if (3) was the thing we agreed upon (and if it will help us > to detect issues in Horizon) but the rest of options definitely make sense > to me. > I think that's reasonable - moving the tests to tempest will

Re: [openstack-dev] [Horizon] On testing...

I'm not sure if (3) was the thing we agreed upon (and if it will help us to detect issues in Horizon) but the rest of options definitely make sense to me. Also there is 5. Parallelize integration tests. On Wed, Jul 20, 2016 at 4:28 PM Richard Jones wrote: > Hi folks, >

[openstack-dev] [Horizon] On testing...

Hi folks, Sorry I didn't make the meeting this morning :-( We touched on testing at the mid-cycle and again it came up in the meeting this morning. We identified two issues: 1. Our integration test suite cannot grow to too many more tests because they take too long to run (and get auto-killed).

[openstack-dev] [Horizon] Accessibility: testing with the keyboard

An easy way to get started identifying accessibility problems is to test using the keyboard. I've made a small update to the wiki describing what to do: https://wiki.openstack.org/wiki/Horizon/WebAccessibility I've open our first accessibility bug, and it's related to keyboard testing:

Re: [openstack-dev] [horizon] Javascript testing framework

On 03/12/13 01:26, Maxime Vidori wrote: Hi! In order to improve the javascript quality of Horizon, we have to change the testing framework of the client-side. Qunit is a good tool for simple tests, but the integration of Angular need some powerful features which are not present in Qunit.

Re: [openstack-dev] [horizon] Javascript testing framework

: Tuesday, December 3, 2013 10:32:17 AM Subject: Re: [openstack-dev] [horizon] Javascript testing framework On 03/12/13 01:26, Maxime Vidori wrote: Hi! In order to improve the javascript quality of Horizon, we have to change the testing framework of the client-side. Qunit is a good tool for simple

[openstack-dev] [horizon] Javascript testing framework

Hi! In order to improve the javascript quality of Horizon, we have to change the testing framework of the client-side. Qunit is a good tool for simple tests, but the integration of Angular need some powerful features which are not present in Qunit. So, I have made a little POC with the