Skip to main content
Jump to: navigation, search

Orion/Test Pass

< Orion
Revision as of 15:20, 8 June 2016 by Carolyn (Talk | contribs) (Focus on new functionality)

There are two parts to the test pass.

Focus on new functionality

Testing some of these may require more digging and setup than we usually do during a test pass (hoping that item contacts will add additional "How to test" details to help testers get going). If you have questions then ask the item's listed contact.

Feature: Added syntax styling for CoffeeScript, Sass/SCSS, Less, TypeScript, SQL, properties files

  • Contact: Grant
  • How to test: google for some code examples in these languages, paste them in an editor, verify that the syntax styling is reasonable, adapts to changes well, etc.
  • Testers: Chrome: Curtis, Firefox: Libing, IE: Muhammad

Feature: Orion Node Server

  • Contact: SSQ
  • How to test: Build it, run it (see modules/orionode/ for instructions)
  • Testers: Mike, Curtis, Grant

Feature: Enhancements to the standalone "CodeEdit" widget and "in-memory" tern project support on codeEdit widget

  • Contact: Libing
  • How to test: Self-host and ensure that both embeddedEditor/demoBuild/demo/demoTernProject.html and /embeddedEditor/demo/demoCodeEdit.html work (eg.- type some code into the first one and ensure that tern is working there, etc.)
  • Other options for the first page: You can also use for the first test.
  • How to use the codeEdit build: The first page demoTernProject.html requires the latest codeEdit build. Download and drag and drop to /embeddedEditor/demoBuild/demo/editorBuild/ folder. Then use the page embeddedEditor/demoBuild/demo/demoTernProject.html. All details is in the page.
  • Testers: Chrome: Mike, Firefox: Car, Safari: Grant

Feature: ARIA content assist in HTML

  • Contact: Car
  • How to test: Press Ctrl+Space in the context of an HTML element's attributes, use role or aria-* completions. Then press Ctrl+Space within the attribute value's quotes for value proposals. See the ARIA Content Assist blog post for examples.
  • Testers: Chrome: Libing, Firefox: Olivier, IE: Sidney

Feature: Cross-file linting

  • Contact: Mike/Curtis/Olivier
  • How to test: Verify the ability to determine whether a function is used across scripts
  • Testers: Chrome: Eric, Firefox: Anthony, IE: Jenny

Feature: ES6 support

  • Contact: Mike/Curtis/Olivier
  • How to test: Learn about new ES6 features, then verify our parsing, ES6 module resolution, occurrences, content assist, definitions, templates, etc.
  • Testers: Chrome: SSQ, Firefox: Eric, Safari: Muhammad

Feature: .eslintrc.* support

  • Contact: Mike/Curtis/Olivier
  • How to test: The format of these is described at All of the formats except for *.YML and *.YAML are supported. There are no existing examples, aside from the ESLint wiki or an existing github repo that has one. Another important thing to test here is file precedence - The ESlint wiki explains the ordering of the files if more than one of them exists.
  • Testers: Chrome: Grant, Firefox: Olivier, Safari: SSQ

Feature: Definition files in projects

  • Contact: Mike/Curtis/Olivier
  • How to test: Examples of definition files are in org.eclipse.orion.client/bundles/org.eclipse.orion.client.javascript/web/tern/defs/. Definition files must be placed in the .definitions folder in the root of the project and added to the .tern-project file in the libs section (again see the Orion client repo for an example).
    • One example to test: open server.js and hover over / use assist for the node lib compression. You get support for the library solely because it has a definition file. So if you remove the definition file and reload the page, you lose support for the library. There is already a bug open to have the tool automatically reset on changes to the .definitions folder.
  • Testers: Chrome: Anthony, Firefox: Sidney, IE: Car

Feature: Many new configuration linting rules: tern plugins not loaded, envs in use that don't match project configuration, etc. Also, quick fix for all of these, and gratuitous brackets, semi, etc.

  • Contact: Mike/Curtis/Olivier
  • How to test: Mike/Curtis/Olivier can you point at some configuration files to serve as starting points? Or projects that have such files?
  • Testers: Chrome: Jenny, Firefox: Car, IE: Eric

Test for breadth

Visit all of the pages, try to exercise most of the functionality, do some real development (not just clicking around). Keep an eye on the debug console for error messages. Browsers:


  • Libing
  • Sidney
  • Mike
  • Olivier


  • Anthony
  • Jenny
  • Curtis

Firefox (slightly older version):

  • Eric


  • Grant
  • SSQ


  • Car
  • Muhammad

Back to the top