Code Challenges Authoring Cheat Sheet
Ruby + rspec Code Challenge
- LE authoring:
- LE preview:
- Hit the
+in sidebar to create a code challenge
- Choose your prompt, configuration, default file, backend type, etc.
- Click on workspace to get to authoring mode:
- Preview shows you what user will experience in LE:
NEW!No need to specify a workspace slug in Author. LE auto-creates the workspace.
- Use the file nav and code editor to create and edit workspace
- Save the workspace with
- Go back to last saved workspace with
- Folder upload tool lets you upload an entire folder from your file system
Test type <> Workspace type mapping
|Test Type||Workspace Type||Notes|
|Component Test||all||WebBrowser component tests (
|Java JUnit Test||Java||-|
|Mocha Test||Babel, BabelNode, Node||Use
|Python Test||Python 3||_|
|R Script Test||R||_|
|RSpec Test||Ruby, Ruby on Rails||-|
- Create a backend type and default filename before you create the workspace.
?latest_draft_applied=trueto view unpublished changes in preview/authoring view
- Preview will not work until you have created a workspace in authoring.
- If you rename the default file in authoring, you'll need to change the filename in Author
- Make sure your backend type supports your test type (Author does not validate this)
- Be sure to remove the test file before you save your final changes
- In you switch from preview mode to authoring mode, hit the
Reseticon to confirm what the user will see
- You may be able to see the test code in authoring mode, but editing it there will not change the test.
- Component tests are limited to CodeEditor and OutputTerminal
- Don't forget to add a
tests/directory to the workspace if you use mocha / php tests.
- Babel containers require an entry file called
index.jsin order to run