You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (Jira)" <ji...@apache.org> on 2021/04/10 15:51:00 UTC
[jira] [Updated] (DIRSTUDIO-1274) Rework UI tests
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seelmann updated DIRSTUDIO-1274:
---------------------------------------
Description:
The SWTBot based UI tests are an important asset, the Studio test coverage is based on that.
Those tests grew over the last years and some technical debt accumulated:
* Most UI tests run against ApacheDS only.
* Recently additional tests against OpenLDPAP and 389ds were added. However those are separate test classes and only very few tests exist and test code is duplicated.
* There are several LDIFs that serve as test fixture for different tests, the increased amount makes it hard to maintain and duplication exists.
* The ApacheDS test framework is used to run an LDAP server. This framework is currently changed to JUnit5, so changes in the Studio tests are expected too.
It would be nice to run all UI tests against all LDAP servers
Goals:
* Allow to run all (or most) tests against multiple LDAP server (currently ApacheDS, OpenLDAP, 389ds, more can be added)
* As there are subtle differences between LDAP servers the tests must be aware of the server type to adjust requests or assertions
* Create a simpler and unified test fixture
* Switch to JUnit 5
was:
The SWTBot based UI tests are an important asset, the Studio test coverage is based on that.
Those tests grew over the last years and some technical debt accumulated:
* Most UI tests run against ApacheDS only.
* Recently additional tests against OpenLDPAP and 389ds were added. However those are separate test classes and only very few tests exist and those duplicate test code.
* There are several LDIFs that serve as test fixture for different tests, the increased amount makes it hard to maintain and duplication exists.
* The ApacheDS test framework is used to run an LDAP server. This framework is currently changed to JUnit5, so changes in the Studio tests are expected too.
It would be nice to run all UI tests against all LDAP servers
Goals:
* Allow to un all (or most) tests against multiple LDAP server (currently ApacheDS, OpenLDAP, 389ds, more can be added)
* As there are subtle differences between LDAP servers the tests must be aware of the server type to adjust requests or assertions
* Create a simpler and unified test fixture
* Switch to JUnit 5
> Rework UI tests
> ---------------
>
> Key: DIRSTUDIO-1274
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1274
> Project: Directory Studio
> Issue Type: Test
> Reporter: Stefan Seelmann
> Assignee: Stefan Seelmann
> Priority: Major
>
> The SWTBot based UI tests are an important asset, the Studio test coverage is based on that.
> Those tests grew over the last years and some technical debt accumulated:
> * Most UI tests run against ApacheDS only.
> * Recently additional tests against OpenLDPAP and 389ds were added. However those are separate test classes and only very few tests exist and test code is duplicated.
> * There are several LDIFs that serve as test fixture for different tests, the increased amount makes it hard to maintain and duplication exists.
> * The ApacheDS test framework is used to run an LDAP server. This framework is currently changed to JUnit5, so changes in the Studio tests are expected too.
> It would be nice to run all UI tests against all LDAP servers
> Goals:
> * Allow to run all (or most) tests against multiple LDAP server (currently ApacheDS, OpenLDAP, 389ds, more can be added)
> * As there are subtle differences between LDAP servers the tests must be aware of the server type to adjust requests or assertions
> * Create a simpler and unified test fixture
> * Switch to JUnit 5
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org