An easy one #
|
|
This one’s pretty trivial; we just implement the opposite steps to the ones we did for “Disallow connection if server in Starting mode”. In truth, it’s somewhat redundant; if this didn’t work, none of the login tests would work, but we’ll leave it here for completeness.
7 scenarios (7 passed)
33 steps (33 passed)
2m14.275s
useradd #
|
|
To get the server in Locked mode, we need to have an admin log in and lock it. Let’s see what allows
a user to use /lockserver
…
|
|
impLevel
is in the Player
table, so we need to make sure we have an Account and a Player. We
start with an
ugly-but-it-works solution,
but then split it up into reasonable methods:
|
|
|
|
|
|
|
|
After this, the steps for getting into the chat and issuing the lock command are pretty trivial.
8 scenarios (8 passed)
42 steps (42 passed)
2m5.928s
Slow going #
Making such slow progress, it seems like I’ll never get a decent set of tests up and running. But we’re building up an inventory of reusable code that will make future tests easier to implement.
The big question is: How do we approach such a big test project, really, and how do we organize the work? I’ve been considering that, and think I have an approach to try. Tomorrow.