Debugging doesn't work like I want it to!
-
And your syntax is horrible and you should feel bad.
That's something where we'll disagree.
-
-
It's Tcl, isn't it?
Yep, the language that lots of people seem to hate because it's syntax is too simple for them and the semantics too predictable.
-
But, but... it uses {}s instead of ()s. Intolerable!
-
It's nice to give tests a name; useful for reporting
test model-123 "model has right number of failures" -body {
model get -failcount
} -result 1
Vs, say...
describe Bowling, "#score" do it "returns 0 for all gutter game" do bowling = Bowling.new 20.times { bowling.hit(0) } bowling.score.should eq(0) end en
it's syntax is too simple for them
DIAF.
Spleling / Grammor awarded - b
-
DIAF
Not really seeing much in the way of significant difference between the two, really, other than the Ruby one being longer (because it's doing more tests)?
-
Yeah, that's something that is actually quite nice about Ruby, that there seems to be a culture of caring about the stuff like that (although my main exposure to Ruby has been the Dicsourse project, so I haven't seen much of it myself), although there also seems to be a culture of being an absolute smartypants, which sometimes results in a kind of magic-eye effect for me, where the way the code flows makes me want to parse it as english instead of as code and I end up staring at it for way too long trying to figure out what's going on.
I think my problem with
it "returns 0 for all gutter game" do ... end
might not have happened if they would have usedtest
as the method name instead ofit
.I agree with you about the flow of QUnit vs JUnit, although I suppose that trwtf here is positional parameters: this seems like a place where something like
actual = model.get("failCount"), expected = 1
would be a lot more helpful.
-
hey would have used test as the method name instead of it
+do. Verbs make better names for methods than pronouns.
(Also, ooh, so it's a method!)
-
-
In that case, she can have a spellar/gramming flag!
-
And I have somehow managed to flag myself again...
-
-
I would try and blame Discourse, but seeing as AFAIK nobody else has managed that even once... @CodingHorrorBot
-
@tar Is Doing It Wrong™
-
try and
Try to, you cretin. You are definitely doing it wrong.
Also: It was very small, but I see what you did there.
-
Some grammarians label try and as incorrect when really it is just very informal
Not going to risk flagging you though...
-
"Try and $verb" would make sense if you were using as a shortened form of "Try to $verb and succeed in doing so." Otherwise, http://www.sadtrombone.com/?play=true.
-
'Try to blame Discourse and succeed in doing so'?
-
Of course. When was the last time Discourse wasn't to blame? null
-
"I tried and failed to understand Jeff's latest blog entry"
-
I hate how junit assertion failure messages work.
We switched from TestNG to JUnit last year. Similar thing. Rather than swap around the 8 squajillion tests we already had written I made a wrapper class for Assert that did it for me, and changed the imports to that instead of the normal JUnit Assert.
-
-
In that case, she can have a spellar/gramming flag!
i'm going to agree with you on that one. ;-)
-
I would try and blame Discourse, but seeing as AFAIK nobody else has managed that even once...
hi! i've done it. just ask @boomzilla!
-
-
-
-
Except I didn't name names, so only Han'd, maybe.
hmm true.... and i think i'm not the only other one that has accidentally flagged their own post before either.... ;-)
-
-
Heh, so there is something off about the flagging UI, then?
maybe. i'm calling PEBKAC though. was simply not paying enough attention to what i was flagging, and there is a legitimate case for flagging your own posts.
-
-
legitimate case for flagging your own posts
Trying for a badger and hoping the mods don't realise one of the flags is your own?
-
IME intentionally flagging yourself for a whoosh gets it awarded faster.
-
IME intentionally flagging yourself for a whoosh gets it awarded faster.
And you would know!
-
The most legitimate self-flag would be accidentally miscategorizing your topic without having TL3 and thus issuing an OT flag.
-
Let's review:
Vs, say...
<pre>
describe Bowling, "#score" do it "returns 0 for all gutter game" do bowling = Bowling.new 20.times { bowling.hit(0) } bowling.score.should eq(0) end en
</pre>
it's syntax is too simple for them
DIAF.
Spleling / Grammor awarded - b
Discourse ate the flags @discoursebot in the admin interface, but these guys flagged the post:
-
@boomzilla - Last Day Without A Discourse Bug: null
-
- Weird that discourse notified me about this post.
- Weird that those guys thought that was a response to the spelling error, not the insufferable smugness.
-
The most legitimate self-flag would be accidentally miscategorizing your topic without having TL3 and thus issuing an OT flag.
also IIRC flagging your own post as spam automatically hides it, so you can use it to make post go away right now if it has something like a photo with EXIF data that it shouldn't have.
-
....I like badges :) I plead the fifth on what I was reacting to
-
1) Weird that discourse notified me about this post.
Its a bug that I discovered in /t/1000:
@aliceif said:Yes, codeblocked quotes trigger notifications.
Basically, every post that contains[quote="name, post:1234, topic:1000"]
anywhere in its raw triggers a quote mention for "name".
-
also IIRC flagging your own post as spam automatically hides it, so you can use it to make post go away right now if it has something like a photo with EXIF data that it shouldn't have.
Be sure to say why you're flagging it. That way a moderator can make sure the post is deleted without agreeing to your flag, which we do with actual spam, and will count against you for stuff like TL3 promotion criteria. Not that we probably wouldn't ask what's going on if you just flagged your own thing as spam.
-
Be sure to say why you're flagging it.
not an option with flagging as OT, inappropriate or spam....
and i know flagging with freetext doesn't autohide....
:-(
-
-
-
not an option with flagging as OT, inappropriate or spam....
Oh, right. Well...Doing It Wrong.
I imagine I'd contact the poster in this case. A separate PM to mods might be a good idea, then, just to be sure.
-
Hey I know! Why don't we spend a billion posts talking about meta-bullshit! "Hey Sandy, what's the latest gossip on all the FLAGS?!" "Hey Cherise, I heard that Fred flagged Ted for flagging Emily, but when Emily tried to tell a mod to flag Greg to flag Ted, Fred flagged her too!" "OMG! How many badges did she get!"
-
Why don't we spend a billion posts talking about meta-bullshit!
And I thought that was the whole point of this forum. Silly me!
-
And I thought that was the whole point of this forum. Silly me!
He's just mad because we're not nitpicking about the kind of stuff he likes to nitpick about, and also nobody's said anything to trigger him for a while (or so I assume, having not caught up yet this morning.)
-
I thought that was the whole point of this forum.
No, it's to break Discourse (and have fun in the process).
While it breaks often with far less than a billion posts, I'm not sure that a billion posts, in and of itself, would break it. Four billion and change, on the other hand...
Onward! For science!