Closed
Description
First:
- Continuous Integration runs all unit and integration tests and fails no test
- Maximum number of compiler warnings are resolved
- Version numbers are verified manually
- Releases depend on the right versions of dependencies (manually verified)
Then the following features need manual testing in Eclipse:
- Eclipse downloads latest stable release from update site https://update.rascal-mpl.org/unstable
- Open a Rascal REPL using the toolbar button
- Can create new Rascal project using the wizard
- Can create new Rascal module using the wizard
- Can edit Rascal file in Rascal project
- Save on Rascal file triggers type-checker
- Rascal outline works
- Rascal navigator works
- Rascal navigator displays working sets
- Rascal navigator displays interpreter's search path
- Clicking links in REPL opens editors and websites
-
rascal>1 + 1on the REPL -
import IO; println("Hello Rascal!");
not in template:
- in editor, click on use of name jumps to definition
- jump-to-definition also works to library modules and inside library modules
- clicking in outline jumps to editor to right position
- syntax highlighting in editor works
- add dependency on another project by editing
RASCAL.MF:Required-Libraries: |lib://otherProject|, import a module and test the type-checker as well as the interpreter for correct resolution -
import demo::lang::Pico::Plugin; registerPico();and test the editor of the example pico files (syntax highlighting, menu options) - open tutor view and test the search box
- open tutor view and test browsing the documentation
-
import demo::lang::Pico::Plugin; rascal>:edit demo::lang::Pico::Plugin - edit a .concept file, save it and watch the preview in the Tutor Preview view
- Tutor Preview "edit" button opens the corresponding concept file of the currently visited Concept URL
- Tutor Preview Forward/Back/Refresh buttons work