do we have any plans for any kind of integration testing for our UI? I am thinking of Protractor or Selenium, but perhaps there are better options. Currently we have a lot of unit tests, but nothing that tests the whole thing as far as my knowledge goes. I personally was affected by this, when I broke the whole UI, although all unit tests would happily pass (I added methods to a wrong class basically).
I'm just throwing this out there as a discussion. Starting it was a retrospective item of ours, from 3 weeks ago (had other things on my plate and I've let this one slip, sorry!). So, let me know what you think about our current testing approach in the UI.
Regards,
Paweł
···
–
Paweł Gesek
Technical Project Manager
/ +48 690 020 875
SolDevelo Sp. z o. o. [LLC]
Office: +48 58 782 45 40 / Fax: +48 58 782 45 41 Al. Zwycięstwa 96/98 81-451, Gdynia
[http://www.soldevelo.com](http://www.SolDevelo.com)
Place of registration: Regional Court for the City of Gdansk KRS: 0000332728, TAX ID: PL5862240331, REGON: 220828585, Share capital: 60,000.00 PLN
I was thinking the same thing! Will post another thread to explain my thoughts in details.
···
On Wednesday, March 22, 2017 at 8:37:01 PM UTC+8, Paweł Gesek wrote:
Hello everyone,
do we have any plans for any kind of integration testing for our UI? I am thinking of Protractor or Selenium, but perhaps there are better options. Currently we have a lot of unit tests, but nothing that tests the whole thing as far as my knowledge goes. I personally was affected by this, when I broke the whole UI, although all unit tests would happily pass (I added methods to a wrong class basically).
I'm just throwing this out there as a discussion. Starting it was a retrospective item of ours, from 3 weeks ago (had other things on my plate and I've let this one slip, sorry!). So, let me know what you think about our current testing approach in the UI.
On Wednesday, March 22, 2017 at 8:37:01 PM UTC+8, Paweł Gesek wrote:
Hello everyone,
do we have any plans for any kind of integration testing for our UI? I am thinking of Protractor or Selenium, but perhaps there are better options. Currently we have a lot of unit tests, but nothing that tests the whole thing as far as my knowledge goes. I personally was affected by this, when I broke the whole UI, although all unit tests would happily pass (I added methods to a wrong class basically).
I'm just throwing this out there as a discussion. Starting it was a retrospective item of ours, from 3 weeks ago (had other things on my plate and I've let this one slip, sorry!). So, let me know what you think about our current testing approach in the UI.
(1) Grouping all the UI end-to-end tests together breaks the modularization of the UI that we are trying to create. I’ll admit it’s easier to test just the reference-UI… but what about implementations that effectively fork the reference-ui? Are implementers expected to build up their own CI frame work for end-to-end testing?
(2) I’m also unsure that we actually need a full ‘web driver’ platform — the UI should only be communicating with a service in “Angular Service” files, and in those cases we need to make sure that both the “Angular Service” and the OpenLMIS Service honor the same service…
My argument here is that its a waste of effort to check if specific page states are loaded or elements shown — since the UI has a layer of abstraction already implemented.
On Wednesday, March 22, 2017 at 8:37:01 PM UTC+8, Paweł Gesek wrote:
Hello everyone,
do we have any plans for any kind of integration testing for our UI? I am thinking of Protractor or Selenium, but perhaps there are better options. Currently we have a lot of unit tests, but nothing that tests the whole thing as far as my knowledge goes. I personally was affected by this, when I broke the whole UI, although all unit tests would happily pass (I added methods to a wrong class basically).
I’m just throwing this out there as a discussion. Starting it was a retrospective item of ours, from 3 weeks ago (had other things on my plate and I’ve let this one slip, sorry!). So, let me know what you think about our current testing approach in the UI.
