RedDot Ruby Conf 2014

RSpec3 para aplicaciones Ruby

Jon Rowe  · 




Extracto de la transcripción automática del vídeo realizada por YouTube.

hi everyone my name is John I want to make one thing very clear for certain members in the audience I am NOT in fact Australian I'm actually from a small cold - island nation off the coast of Europe called Britain I now live in Sydney which is a very large

country in fact you can see Britain is percentage-wise a very small part of the sort of size of Australia and the reason why I'm here talking to you today is I have the honour of being one of the core team members for r-spec so first off hands up if you've

used have you've heard of r-spec that's a good percentage concept if you use r-spec okay cable going well hands up who's heard of version 3 still a good number good the marketing is working hands up if you've used version 3 that is actually

a good percentage of you I'm glad so why is this important why is aspect 3 important in particular so have you all heard of semantic versioning hands up again good so we all know that in patch releases we should only be able fixing bugs in minor releases

we can add new features but we must not make any breaking changes and we know that in major versions we get to make those breaking changes so just just quickly going over the history of aspect because it is actually quite an old and venerable project at this

stage released in 2005 was aspect 0 versions so these are the very first sort of minor versions that were quite frankly a little bit of a hack this is way before my time on the project I'm way before most people who currently maintain its time on the project

that's been through several sets of maintained errs and it wasn't until 2007 a couple of years later that aspect one was released and it became stable you could use it people actually tested products and shipped cool stuff and it took another three

years until a spec 2 was released which is the version that most of you are probably most familiar with at this point in time when it was released we actually reached about 85 different contributors to a spec at this point it had most of the features we all

know and love and it was during this time of course that rails 3 came out and our spec is sort of grown in usage as rails has grown in usage so if we fast forward to 2014 now we actually have at this point a couple of hundred contributors have committed stuff

to a spec and we finally released version 3 which is actually been the product of more than a year's work so why should you care the issues among you will have noticed of course that this talk title contains a pun we expect you to care and even more astute

if you will notice that I slipped up and said should you care I'm sorry there was no happy accident it was in fact the product of engineering for this talk yeah it's because it's the most recent most visible change that we've sort of made especially

around 3 it's not the only change that's in theory but it's the one that most people are now actually noticing the expect syntax if the if this was a blog post the TLDR of this talk would be the releasing version 3 is about cleaning house about

removing deprecated things and making painful recommendations the expect syntax is that one of those painful recommendations a year or two ago I would have been happy should syntax I would have been more than happy to write should you care for this talk just

a quick show of hands who actually uses the expect syntax and who uses the syntax hi Konstantin so we all know what the expects intake looks like so you generally expect something to match some matcher and we all know that the should syntax is it's a slightly

shorter and we expect some object to should match the expect syntax is not actually that new a lot of people refer to it as the new expect syntax it was actually released in July 2012 in aspect 2.11 somehow that kind of escape to other people's notice

and even before that you could use it to write block expectations in fact you had to if you wanted to test that you were raising errors currently but in three-point mile x as we've 33.0 series it becomes the recommend a recommended syntax it now has full

[ ... ]

Nota: se han omitido las otras 2.015 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.