ConfigModule¶
Bootstrap configuration submodule mounted at /_test/config. Carries
the per-process session state and exposes the two endpoints the runner
uses to acquire/release the session token.
ConfigModule
¶
Bases: Module
Bootstrap configuration module mounted under /_test/config.
Holds the per-process session state as class attributes and exposes two endpoints:
POST /json/_test/config/status— verify the runtime is consistent (dev server + correct datastore database), then read or create the session token entity in the test database and return it. POST-only to block drive-by GETs from another browser tab on the same machine (CORS preflight stops the cross-origin call).POST /json/_test/config/finish— verify the runtime, delete the token entity, clear the in-process token.
Source code in src/viur/testing/_test/config.py
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 | |
__init__
¶
__init__(moduleName: str = 'config', modulePath: str = '_test/config', *args: Any, **kwargs: Any) -> None
Refuse to instantiate unless the runtime is in test mode.
Defense in depth: :class:~viur.testing._test.TestModule already
checks both conditions before constructing the container, but a
host project might bypass the container and mount ConfigModule
directly. The same two guards are repeated here so that a direct
mount cannot accidentally end up in production or run before
:func:viur.testing.activate has wired the datastore client.
Source code in src/viur/testing/_test/config.py
is_active
classmethod
¶
has_token
classmethod
¶
current_namespace
classmethod
¶
Datastore namespace this process is scoped to, or None for
the default namespace.
set_active
classmethod
¶
Mark the process as test-mode active.
Idempotent for matching (database, project_id, namespace);
refuses to silently overwrite a mismatching prior activation.
namespace="" is normalised to None — same convention as
:func:viur.testing.activate and the VIUR_TESTING namespace
part. Without this normalisation a direct call with the
empty string followed by an :func:activate-driven call with
None (or vice-versa) would falsely report a mismatch.
Source code in src/viur/testing/_test/config.py
set_token
classmethod
¶
Record the current session token. Requires prior :meth:set_active.
Source code in src/viur/testing/_test/config.py
clear_token
classmethod
¶
register_status_hook
classmethod
¶
Register a project-side callback that fires inside /_test/config/status.
The hook is invoked after the token has been issued and the
in-process state primed, but before the JSON response is
serialised. If it returns a dict, the entries are merged into
the response payload (later hooks win on conflicting keys).
Side effects on viur.core.conf are allowed — useful for
seeding project-specific config that every test relies on.
Registrations survive across calls to :meth:reset only if
the host re-runs the registration; reset() clears the
hook list along with the rest of the state.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
hook
|
Callable[[], dict | None]
|
A zero-argument callable returning |
required |
Source code in src/viur/testing/_test/config.py
register_finish_hook
classmethod
¶
Register a project-side callback that fires inside /_test/config/finish.
Same shape as :meth:register_status_hook: optional dict
return value is merged into the finish response.
Source code in src/viur/testing/_test/config.py
reset
classmethod
¶
Clear all state. Intended for tests only.
status
¶
Begin (or resume) a test session.
Reads the token entity from the test database; creates it on first call. Updates the in-process state so the request validator starts accepting the token. Returns the full session info, including the token, to the runner.
POST-only on purpose: a third-party browser tab on the same machine cannot issue a cross-origin POST without CORS preflight, so it cannot drive-by trigger a session through this endpoint.
Source code in src/viur/testing/_test/config.py
enter
¶
Arm a manual browsing session by setting the token cookie.
Reached by a plain GET navigation (address bar, link, reload)
before any cookie exists — hence a bootstrap path. Reads/creates the
session token, primes the in-process state, and sets the
viur-test-token cookie. Afterwards every request the browser makes
— including hard navigations and server-rendered pages — carries the
cookie, so the developer can browse the test instance directly without
a header-injecting proxy or browser extension.
GET (not POST) on purpose: you navigate to it. A cross-site drive-by
could trigger it, but the resulting cookie is SameSite=Strict and
scoped to this (dev-only, localhost) host, so it cannot be used from
another site — see the security note in the README.
Source code in src/viur/testing/_test/config.py
finish
¶
End the current test session.
Deletes the token entity from the test database, clears the
in-process token and expires the cookie. Test-mode itself stays
armed — the next call to :meth:status/:meth:enter will provision
a fresh token.