I wanted to start looking at alternatives to our current set of cucumber feature tests. At the moment on the web team we're using using FireWatir and Capybara. So I though I'd take at look at what was available in Node.js. Many people think it's strange that a .Net shop would use a something written for testing Ruby or even consider something that isn't from the .Net community. Personally I think it's a benefit to truly look at something form the outside in. Should it matter what you're using to drive your end product or what language your using to test it? Not really. So what are the motivations for moving away from Ruby, Capybara and FireWatir? In a word 'flaky', we've had heaps of issues getting our feature tests, AATs and smoke tests reliable. When it comes to testing, consistency should be king. They should be as solid as your unit tests. If they fail you want to know that for definite you've broken something, rather than thinking it's a problem with the webdriver. It is with this aim in mind that I started looking at the following. Cucumber.js is definitely in it's infancy, there's lots of stuff missing but there's enough there to get going. Zombie.js is a headless browser, it claims to be insanely fast, no complaints here.
Hack24 API Challenge
This Spring, on the 2nd and 3rd of May, 7digital are proudly sponsoring a new hack day, set up by the Tech Nottingham community - Hack24.
During this 24 hour coding competition, teams of 4 compete to win exclusive prizes, by showcasing their innovative ideas and raw tech talent!
Set in Nottingham's Creative Quarter, this will definitely be an exciting Hackathon to be a part of.
How to get involved?
Context is key to the new wave of music applications. All you can eat music or massive download catalogues are hard to navigate and only let people discover what the retailers think they should. With the onset of wearable technology, open access to contextual data from the internet of things and the general increase in availability of processable data, we can now inform decisions in real-time based on the context in which that person, action or event exists.
Imagine that your music choices could be informed by the weather, or the city you're currently in, or the fact that your friends are all talking about the latest band. What if your music app knew you were running, or cycling, or dancing? Consider that you might want to only listen to rock, or classical, or Christian music or music from bands formed in Nottingham. We have 32 million available tracks to play, but you'll not want to listen to all of them (that's about 369 years of listening) so picking themes is important, and playing them based on the listeners current situation makes them even more important.
The 7digital API allows you to search, list by genre, purchase, preview and stream from our worldwide music catalogue. Couple this with another API or data source, using our partners like MusicBrainz, our matching API, or by combining another API through text searching, and you should be able to create something unique.
Entrance is FREE, we'll take care of the logistics, so all you have to do is sign up for the Hack here!