Repeat It

A User Action Simulator Chrome Extension

Installation

1. Clone this repo
2. Visit chrome://extensions in Chrome
3. Select Developer Mode
4. Click on Load unpacked extension
5. Select the directory in which this repo is cloned

Steps to create a new Recipe

1. Create a new Recipe.js file (for e.g. MyNewRecipe.js)
2. Create a new entry in the array defined in recipes.json.
3. Before committing run the gulp task scripts so that your recipe is minified and added to the extension (inject.js)

NOTE - Make sure the id of the new entry matches with the global namespace of the recipe. For e.g. window.recipe.myNewRecipe should always have id = myNewRecipe

Recipes to create

1. Fill Question Generic Recipe (should support as many questions as possible)
2. Create Assessment Recipe
3. Create T/F Recipe (CreateAssessmentRecipe, OpenTF (child-recipe), FillTF or FillQuestionRecipe)
4. Create a login recipe (ask extension owner to define params)

Todos

1. Make the search box functional so that recipes can be searched by their title in real-time i.e. search as you type (after initial loading)
2. Load recipes.json only once for the entire browser session
3. Placeholder for search input
4. Create Child-Recipes which has no existence alone but can always be clubbed with actual Recipes
5. Organization of all Recipes and Child-Recipes in directories and corresponding gulp task changes
6. Test to make sure all Recipes are present in inject.js combined and every recipe contains steps
7. Create a video showing installation and usage.
8. When recording show some kind of highlighting in the extension icon and Record button.
9. Create a options page to import/export all/selective recipes/recordings but these won't be available to all extension installations. (Needs fileSystem permission)
10. Upgrade extension to use Backbone so that recipelist can be a Backbone collection with unique recipe ids and appropriate events to update popup.html DOM.
11. Recorded recipes should wait for DOM manipulation and ajax-requests to complete before triggering the next step.
12. Create a wait-step such that the next action should wait unless that many seconds for the QA/Tester to see the expected result
13. Create a way for extension users to see the pre-requisite & description for every extension and then execute it when pre-requisities match. Best would be to create a page on github wiki for every recipe with screenshots and if possible with videos showing how does that particular recipe works.
14. Create a way for recipes to take input for e.g. "Create Assessment with 5 random qTypes" to take what qTypes and assessment-name.
15. Create a way for recipes to define pre-requisities and if not matched then show an error-dialog/alert to the user.
16. Add more steps type (redactor, input, recipe), currently it supports only click
17. Add ability in the UI to add multiple param-sets for a particular Recipe & then use one at a time. (Login - Instructor, Student, Admin)
18. Add created_by and author_link to original author of Recipe and show them in popup.html
19. In popup.html show recently used recipes at the top with search working in the same order.
20. Add .jshintrc and a gulp task to run jshint over all .js files
21. Add File-A-Bug feature in extension popup
22. Create a markdown file explaining types of recipes, procedure to create recipe, params, start & stop callbacks.
23. Create a screencast for every recipe showing how the recipe works and what is the pre-requisite.
24. Add ability to add recipe description in html (add pre-requisities here)
25. Start adding extension .crx to releases so that people can download (don't forget to change the version number with every release)
26. Create a child-recipe to save solution/hint & modify points and use it internally in FillQuestionRecipe
27. Allow user to create custom recipes by combining recipes with parameters.
28. Change params variable in recipes.json to parameterSets and fix all impacts.

RoadMap

1. Ability to record actions and create a recipe at run-time
2. Ability to run these recipes from Selenium (Extension install and execute on console - window.recipe.RecipePlayer(someRecipe)
3. Put this extension in Chrome Store
4. Implement usageCount of every recipe globally (across all installations, probably use a heroku free nodejs-mongo webapp or free mongo with REST API)
5. Implement normalCompletionTime for every recipes' manual execution and record actual execution average across all installations to show how much did we saved.
6. Recipe options and a way to edit options for every recipe and local saving without affecting any other installation.
7. Write a plugin for firefox
8. Create gulp tasks to create packaged extensions to be installed in chrome & firefox, with versions and add them to releases.
9. Add support for creating safari extension and gulp-task to do the same.