blob: 5e2c5c018b5be957dc974fbd6671bb6090df802b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
= Testing the Java EE Developers package
Running manual tests is very expensive. The test cases below should be considered for automation!
NOTE: TODO: Automate tests
Any failure to those test cases should be reported to the Eclipse.org project causing the error, and to the link:https://accounts.eclipse.org/mailing-list/epp-dev[EPP mailing-list].
There is room for improvement in these test cases (more test cases, more detailed steps). Feel free to contribute!
== How to test the Eclipse IDE for Javascript Developers package
=== Startup
. Startup package on a new workspace
. Check: error log doesn't report issue
=== New Static Web Project enables HTML, CSS and JS
. Create a new Static Web Project
. Create/Open an HTML file => Check completion, highlighting and other features are enabled
. Create/Open an CSS file => Check completion, highlighting and other features are enabled
. Create/Open an JS file => Check completion, highlighting and other features are enabled
=== Import an existing JS project
. File > Open Projects from Filesystem... Pick a JS project such as mathjs (on GitHub), proceed
. Check: Project has the JavaScript nature and right content
=== Editing JS
. From the mathjs project above, pick an interesting .js file
. Check: syntax highlighting, completion... are enabled and work as expected
=== Node/NPM actions
. From the mathjs project above
. Check: Run As actions are available on projet, package.json and work as expected
=== Debug
. From the mathjs project above
. put a breakpoint, start debug
. Check: breakpoint is hit, values are visibile, step into/over and debugger in general works
---
Process last documented by: link:mailto:mistria@redhat.com[Mickael Istria] & link:mailto:nboldt@redhat.com[Nick Boldt]
Official Package Tester: link:mailto:ibuziuk@redhat.com[Ilya Buziuk]
|
