Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
figured this out (I have done other things since then..) and was that I'd used gsub inplace, so lesson learnt.
Maybe.
On the final test case (the one where the string has no white spaces) are you sure you're returning the string: "You just wanted my autograph didn't you?"?
(JavaScript)Using sg.test (Not the actual method, just a reference) to check if the building contains any white space. If it does I'm just replacing it with "". 2 of the 3 test phases work, however the last one that has No white spaces, does not get approved, even if it's supposed to do nothing with it and just print it out the way it is. Any clue how to get around this? (TOtal nEwB)
cheers anyway :)
Sorry I don't have the requisite Ruby skills to help with this issue. Maybe GiacomoSorbi can have a look?
unless I'm missing something (it is late here...), the random Ruby tests arent working properly - they seem to expect "You just wanted my autograph didn't you?" for all of them.
But then if I try and just pass through the random ones, it fails for the correct reason
Theres going to be something really obvious I've done wrong...
Thats exactly what I was doing too :)
I had to check for various non-numbers types so maybe worth printing out the value and type at the top to see what is failing in particular, if you haven't
cor, that was quite hard work! With my solution as well the best optimisation I found appeared to be using python3 - saved about a third of the time... Anyways, cheers for the challenge :)
cool :)
Forcing it to be a string is a terrible idea.
Javascript provides you with a NaN value specifically for this sort of case.
So to speak none is really essential but I added them just because it reflects the nature of arguments in the test cases.
OOx is right you need to return
NaN
as a string, I have also specified that in the description.this confused me for a bit - it should be 'NaN' as a string, not actually NaN, being returned
Testing for Divident(D)=67 & Divisor(d)=0 -
Expected: NaN, instead got: NaN
This test case is failing ...
Loading more items...