[
https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi...
]
Pavol Srna commented on JBIDE-23321:
------------------------------------
The tests itself are relatively easy to implement because we have some integration tests
for nodejs debugger in JSDT. The problem with openshift is that until now we do not have
working environment in central-ci. So I started working on that first.
There are basically 3 options:
# use external openshift server
# run cdk
# run minishift
Option 1) is not very reliable for tests - the server may be down during tests execution,
performance may vary according to the current load, the tests need to cleanup etc.
Option 2) is good, but it has more dependencies than Option 3), eg. vagrant etc.
Option 3) easy to run, only kvm dependency. But there are no openshift templates
deployed.
I'm working on option 3 POC.
Integration tests for OpenShift Node.js debugger
-------------------------------------------------
Key: JBIDE-23321
URL:
https://issues.jboss.org/browse/JBIDE-23321
Project: Tools (JBoss Tools)
Issue Type: Task
Components: javascript, openshift
Affects Versions: 4.4.2.AM1
Reporter: Ilya Buziuk
Assignee: Pavol Srna
Fix For: 4.4.2.AM3
Node.js Debugging support implemented as part of
https://issues.jboss.org/browse/JBIDE-22225
Should be covered with red deer integration tests. Basically, test coverage of Node.js
Debugger facilities already covered with red deer in JSDT project -
https://git.eclipse.org/r/#/c/82836/
However, implementing smth. similar for OpenShift will be much trickier. Basically,
there is an integration test
*org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is
used for server adapter publishing. For now this test is not sustainable due to
https://issues.jboss.org/browse/JBIDE-23005 .
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)