You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Kalinin (JIRA)" <ji...@apache.org> on 2018/03/13 09:56:00 UTC
[jira] [Assigned] (IGNITE-7895) Web console: revise unit tests
[ https://issues.apache.org/jira/browse/IGNITE-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Kalinin reassigned IGNITE-7895:
-----------------------------------------
Assignee: Ilya Borisov (was: Alexander Kalinin)
> Web console: revise unit tests
> ------------------------------
>
> Key: IGNITE-7895
> URL: https://issues.apache.org/jira/browse/IGNITE-7895
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Kalinin
> Assignee: Ilya Borisov
> Priority: Major
> Fix For: 2.5
>
>
> *The issue:*
> Current web console unit tests run inside Karma and PhantomJS, but this setup adds unnecessary overhead of running simple JS inside browser instead of NodeJS. We _can_ alter the setup in order reduce the overhead, but I think we can also use current setup to [unit test AngularJS directives|https://code.angularjs.org/1.6.0-rc.2/docs/guide/unit-testing#testing-directives] which might require the browser environment.
> *What to do:*
> Investigate AngularJS directive/component unit tests, see if it can run in NodeJS or it requires the browser as a runtime environment. If component unit tests can run in NodeJS, simplify the setup so all unit tests run in it. If component unit tests can only run in browser, add a sample component/directive unit test, we should really write more of those.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)