mottaquikarim/spectacles
initial spec for how content should be defined for problems / tests
JavaScript
Issues
- 1
Automatically create PR from Workspace
#43 opened by mottaquikarim - 0
TravisCI script to assert spec is valid
#44 opened by mottaquikarim - 0
Implement OAuth2.0
#42 opened by mottaquikarim - 1
- 3
- 1
- 1
Implement CI/CD pipeline
#12 opened by mottaquikarim - 0
*SUPER IMPORTANT*: implement webhook when merging to master that recomputes the .contentrc
#14 opened by mottaquikarim - 1
Set up simple testing framework
#22 opened by mottaquikarim - 1
- 1
Set up codeclimate for test coverage
#24 opened by mottaquikarim - 1
Configure the `npm run-script udpate-contentrc` command to run in Travis CI `after_success`
#26 opened by mottaquikarim - 0
envvars vs envvars.sample
#33 opened by mottaquikarim - 0
Write Functional tests
#31 opened by mottaquikarim - 0
Functional Tests Framework
#30 opened by mottaquikarim - 0
Get unit test coverage up to 100%
#27 opened by mottaquikarim - 0
On `npm run-script new-problem` or `npm run-script update-problem`, run the express app and open URL with UUID in browser
#7 opened by mottaquikarim - 1
Implement the `update-problem` script
#8 opened by mottaquikarim - 0
Implement human readable routes for the FE
#19 opened by mmosayed - 2
- 0
- 0
Implement tagging support
#10 opened by mottaquikarim - 0
Update FE app to implement basic CRUD functionalities: *esp* the ability to list all created problems
#9 opened by mottaquikarim