module Bezel::Testing

Testing an application through its endpoint, in the test's own task, without sockets: requests built in memory go through every plug, the router and the actions, and the responses come back to be checked.

class TPages < Bezel::Controller
  controller
  def home(conn: Bezel::Conn) -> Bezel::Conn = render(conn, Bezel.html { |h| h.h1("Hello") })
end

class TRouter < Bezel::Router
  routes do
    get "/", TPages, :home
  end
end

class TApp < Bezel::Endpoint
  def self.plugs -> Array[Bezel::Plug] = [TRouter.new]
end

res = Bezel::Testing.get(TApp, "/")
Bezel::Testing.html_response(res, 200).has_text?("Hello")   # => true

Testing.get and friends make one request each; a Testing::Client keeps cookies between requests, as a browser does (sessions, the flash, a login), and follows redirects. The applications they run in are test ones whose CSRF check is off (App#skip_csrf, a flag the program sets and prod refuses), so that a test posts without a token; Testing.app(skip_csrf: false) tests the check itself.

The response helpers check the status and raise Test::AssertionFailed otherwise, with the body's start, so that a test fails as an assertion does.

src/testing.qz:35

Classes and modules

• Bezel::Testing::Client A browser for tests: requests to one endpoint (the Host www.example.com), keeping the cookies the responses set (a Max-Age of zero or less deletes one; Expires is not read), sending them with the next.
• Bezel::Testing::Doc A parsed HTML page for tests to query (Testing.html_response): its elements as a tree, found by a small selector language:
• Bezel::Testing::Node An element of a Testing::Doc (or its root, without a tag), or a text.

Class methods