[
https://issues.apache.org/jira/browse/SOLR-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104642#comment-18104642
]
Jan Høydahl commented on SOLR-8474:
-----------------------------------
I'm giving AI the task of putting together some basic test coverage for the old
Admin UI, since it will live with us for some time still. This is more or less
a one-shot effort, if I don't get payback within a hour, I'll abandon it :) I
have asked Claude Fable to
* Develop Java-only Junit based tests for the UI Dashboard page as a start
* It will use Selenium as framework
* The JettySolrRunner will get an option to enable AdminUI (by default it does
not serve one)
* There will be a new base test class AdminUiTestBase from which all tests
will derive
* It will not install any NodeJS, browsers or anything. If a Chrome instance
is not already installed on the system, tests will just be skipped. Thus in a
CI we need to make sure Chrome is installed before running these tests
* Once a first test is developed and runs green, will add more
PR will be put up here once I have something. This is a throwaway spike. If it
works and provides value, then we can keep it for the life of the Angular
AdminUI, if not, just drop it.
> Test Framework for functional testing Angular UI
> ------------------------------------------------
>
> Key: SOLR-8474
> URL: https://issues.apache.org/jira/browse/SOLR-8474
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Affects Versions: 5.4
> Reporter: Upayavira
> Assignee: Jan Høydahl
> Priority: Major
> Attachments: SOLR-8474.zip
>
>
> The Solr UI has no tests. This is less than ideal. This ticket is aimed at
> facilitating discussion around such a test framework for
> functional/end-to-end testing components within the Angular UI.
> Having a unit testing framework will encourage developers of the UI to make
> more modular, and thus hopefully cleaner, code, as well as providing a means
> to identify regressions.
> For functional testing, I am proposing a Karma/Protractor/Jasmine combination.
> Karma runs the tests, as with the Unit testing framework, Protractor
> interacts with the pages effectively via a programmable browser (click here,
> enter there, confirm that) whilst Jasmine provides a BDD style syntax for
> constructing the tests themselves.
> My proposal is that, for functional tests, we will fire up a full Solr server
> via the existing test framework, then invoke Karma/Protractor within that
> context. That will mean that the functional tests will be interacting with a
> real Solr instance, presumably with real data in it.
> Karma/Protractor/Jasmine can be installed by npm, which would become a
> dependency for the Lucene/Solr build process, as for SOLR-8473.
> As with SOLR-8473, there will be a dependency on either Chrome (and a UI such
> as X) or a UI-less browser such as PhantomJS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
