Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Testing / Code Quality #62

Open
maxtilford opened this issue Sep 21, 2011 · 0 comments
Open

Better Testing / Code Quality #62

maxtilford opened this issue Sep 21, 2011 · 0 comments

Comments

@maxtilford
Copy link

TODO - in no particular order

  • N/A - all up to date Update all are testing related libraries
    • Rspec
    • RR
    • Capybara?
    • FactoryGirl
    • Forgery
    • DONE autotest (maybe we should switch to Guard, so that we're running the jslinter as well)
  • Figure out a standard method for writing tests. We seem to have a couple different styles at the moment.
  • Refactor to make pain points easier to test.
    • Simplify any remaining complex controllers
  • Test the javascript!
    • Jasmine?
  • Things that need to be tested
    • All the mails
    • The api, the current testing is very general and basic. We need to test that each api method is doing what it purports to be
    • Models - relationships between Users, Feeds, Announcements and Events should be standardized
    • The frontend Backbone code
    • Registration should be more heavily tested
    • Feed registration should be heavily tested
  • Organize/clean up the mess that is application controller.
    • some of the stuff in there might make sense as rack middleware, esp. the subdomain redirection
@ghost ghost assigned maxtilford Sep 21, 2011
@maxtilford maxtilford reopened this Sep 22, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant