Integration tests for UI

11 views
Skip to first unread message

Paweł Gesek

unread,
Mar 22, 2017, 8:37:01 AM3/22/17
to OpenLMIS Dev

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.

Regards,
Paweł


--

Paweł Gesek
Technical Project Manager
pge...@soldevelo.com / +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

Place of registration: Regional Court for the City of Gdansk KRS: 0000332728, TAX ID: PL5862240331, REGON: 220828585, Share capital: 60,000.00 PLN

pf...@thoughtworks.com

unread,
Mar 23, 2017, 6:14:45 AM3/23/17
to OpenLMIS Dev
I was thinking the same thing! Will post another thread to explain my thoughts in details.

pf...@thoughtworks.com

unread,
Mar 23, 2017, 6:32:33 AM3/23/17
to OpenLMIS Dev


On Wednesday, March 22, 2017 at 8:37:01 PM UTC+8, Paweł Gesek wrote:

Nick Reid

unread,
Mar 27, 2017, 10:38:43 AM3/27/17
to pf...@thoughtworks.com, OpenLMIS Dev

I have two concerns:


(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.


-- nick --


Nick Reid | nick...@villagereach.org
Friendly Neighborhood Spiderman, Information Systems Group


VillageReach Starting at the Last Mile
2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA
CELL: +1.510.410.0020
SKYPE: nickdotreid
www.villagereach.org



From: openlm...@googlegroups.com <openlm...@googlegroups.com> on behalf of pf...@thoughtworks.com <pf...@thoughtworks.com>
Sent: Thursday, March 23, 2017 3:32:33 AM
To: OpenLMIS Dev
Subject: [openlmis-dev] Re: Integration tests for UI
 
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/ddf3a42a-1658-4eef-a3af-444fa8e25804%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages