"This extension provides a generic way for you to define different types of relationships between your products, by defining a RelationType for each type of relationship you'd like to maintain."
The extension is forked for older version of Spree but need to be updated to work seamless with Spree 2.x. Even if we made the tests pass on Travis doesn't mean that it fully work due to poor test coverage.
We have upgraded most part of the extension but due to our schedule we need assistant to write tests because it has poor test coverage. Capybara feature specs are also required to confirm that the extension hooks into the Spree version correctly.
- Update module so it work with changes in Spree 2.x (if needed)
- Update so views and hooks apply seamless into Spree 2.x
- Rspec tests coverage >= 95%
- Feature specs with Capybara so we know it always there
- Some basic Refactor (if needed)
- JS and CSS in views is ugly, try to move these (if possible)
Note: Don't forget to checkout different branches you might find neat things that can be cherry-picked straight into your working clone and save you some time.
This is a job for anyone that are very comfortable with Rails, RSpec and Capybara. Knowledge of Spree or at least that you can understand its API quick.
How to apply
1, Please checkout the source code of the project before you apply, its open for all so you can just git clone it and test it out.
2, Don't apply please with irrelevant long CV and showcases from your copy & past bin, write a short message with relevant info about the task (we Ruby developers to and like things short and techy).
3, Don't apply please if you think you can include learning Spree in the hours paid, update yourself on your spare time.
4, It would be nice if you send us your Github link and Skype id or best to chat with us on IRC.
We will submit many similar "coffee-break-jobs" based on some of our forks/repositories and looking for right person to assist us with those and some other private extensions.
Its of high importance that you do frequent pull requests and keep your branch updated so I can help out with the trivial stuff and other issues but this job you can probably fit in one pull request.
Spree dev docs: http://guides.spreecommerce.com/developer
- By Skype
- You can also at IRC freenode.org ask for help if you get stuck at #spree