@thomas_witt Something was messed up with the post, we’ve just restored it

Two GETs. The second one is unnecessary. Two failure messages if something goes wrong. I only want to deal with the immediate error. One small step at a time. Nine lines of code Four db records created. I need to create two objects to test ordering. With two test runs, I get 4 objects. With more tests, I get many more objects created. This significantly increases my overall test time for the suite, breaking my concentration and losing everyone money. String programming. Some feel stronger about that eval that happens with “User.ordered”. I’m somewhat ambivalent. I don’t like that I lose syntax highlighting. A pragmatic rule of thumb seems to be: if it can be avoided, it should be. Where do I put new tests? Do I find the perfect context with the perfect setup? At a certain point, nested contexts become unwieldy. I don’t want to scroll 100 lines up to find out where I’m decl...