Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SmokeTestingForMilestone"
(→Simple Steps) |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
== JDT Debug == | == JDT Debug == | ||
| − | + | === Detailed Steps === | |
| + | https://wiki.eclipse.org/Debug/Test_Script | ||
| + | === Simple Steps === | ||
| + | * Launching and debugging of Java Project | ||
| + | 1) Create a Java Project | ||
| + | 2) Create a class with main method | ||
| + | 3) Create a variable of Integer/String type | ||
| + | 4) Create a variable of array type | ||
| + | 5) Create a variable of list type | ||
| + | 6) Perform some operations on the variables and add them in Sysout | ||
| + | 7) Run the program and observe the console | ||
| + | 8) Add a Debug breakpoint on Sysout and inspect the values during debug | ||
| + | 9) Add some Expression in Debug Shell /expression view to inspect at breakpoint | ||
== JDT UI == | == JDT UI == | ||
| + | For Eclipse release: https://www.eclipse.org/jdt/ui/smoke-test/smoke.html | ||
| + | |||
| + | For Java release: https://wiki.eclipse.org/JDKUpdateTesting#JDT_UI | ||
== PDE == | == PDE == | ||
| − | * Create a new PDE plugin project P1 using Hello World Command. Check that | + | * 1) Create a new PDE plugin project P1 using Hello World Command. Check that |
| − | a) The project creation goes fine | + | a) The project creation goes fine |
| − | b) No error in Problem view | + | b) No error in Problem view |
| − | c) Manifest UI is fine | + | c) Manifest UI is fine |
| − | * Create a test project P2 ( with PDE and API tool nature) with exported package and a class in exported package. | + | * 2) Create a test project P2 ( with PDE and API tool nature) with exported package and a class in exported package. |
| − | Export that plugin and put that plugin as baseline. Add a public function. | + | *Export that plugin and put that plugin as baseline. Add a public function. |
| − | a) There should be since tag error and a version error | + | a) There should be since tag error and a version error |
| − | b) Use quickfix to add since tag and update version. | + | b) Use quickfix to add since tag and update version. |
| − | * Add @noinstantiate on that class in previous step and try to instantiate a new plugin project P3 ( with PDE and API tool nature) . | + | * 3) Add @noinstantiate on that class in previous step and try to instantiate a new plugin project P3 ( with PDE and API tool nature) . |
| − | a)You should get a warning that the class cannot be instantiated | + | a)You should get a warning that the class cannot be instantiated |
| − | b)Use quickfix to change the warning to Error and problem view should be change appropriately | + | b)Use quickfix to change the warning to Error and problem view should be change appropriately |
| − | * | + | * 4) Create a test project P4 ( with PDE and API tool nature) with exported package and a record in exported package. |
| − | Export that plugin and put that plugin as baseline. Add a public function. | + | *Export that plugin and put that plugin as baseline. Add a public function to the record. |
| − | a)There should be since tag error. | + | a)There should be since tag error. |
| − | b)Use quickfix to add since tag and update version. | + | b)Use quickfix to add since tag and update version. |
Latest revision as of 02:58, 19 February 2021
Smoke Testing for various components for each milestone
General
JDT Core
JDT Debug
Detailed Steps
https://wiki.eclipse.org/Debug/Test_Script
Simple Steps
- Launching and debugging of Java Project
1) Create a Java Project 2) Create a class with main method 3) Create a variable of Integer/String type 4) Create a variable of array type 5) Create a variable of list type 6) Perform some operations on the variables and add them in Sysout 7) Run the program and observe the console 8) Add a Debug breakpoint on Sysout and inspect the values during debug 9) Add some Expression in Debug Shell /expression view to inspect at breakpoint
JDT UI
For Eclipse release: https://www.eclipse.org/jdt/ui/smoke-test/smoke.html
For Java release: https://wiki.eclipse.org/JDKUpdateTesting#JDT_UI
PDE
- 1) Create a new PDE plugin project P1 using Hello World Command. Check that
a) The project creation goes fine b) No error in Problem view c) Manifest UI is fine
- 2) Create a test project P2 ( with PDE and API tool nature) with exported package and a class in exported package.
- Export that plugin and put that plugin as baseline. Add a public function.
a) There should be since tag error and a version error b) Use quickfix to add since tag and update version.
- 3) Add @noinstantiate on that class in previous step and try to instantiate a new plugin project P3 ( with PDE and API tool nature) .
a)You should get a warning that the class cannot be instantiated b)Use quickfix to change the warning to Error and problem view should be change appropriately
- 4) Create a test project P4 ( with PDE and API tool nature) with exported package and a record in exported package.
- Export that plugin and put that plugin as baseline. Add a public function to the record.
a)There should be since tag error. b)Use quickfix to add since tag and update version.