As mentioned in the Why Athena? page, Athena strongly suggests following the SOLID design principles; especially the Dependency inversion principle in order to create types that are easy to test.

If these principles are followed then any controller/service can easily be unit tested on their own as you would any Crystal type, possibly utilizing ASPEC::TestCase to provide helpful abstractions around common testing/helper logic for sets of common types.

However, the framework also comes bundled with ATH::Spec::APITestCase to allow for easily creating integration tests for ATH::Controllers; which is the more ideal way to test a controller. Many helpful HTTP related expectations are also provided.

require "athena"
require "athena/spec"

class ExampleController < ATH::Controller
  def add(value1 : Int32, value2 : Int32, negative : Bool = false) : Int32
    sum = value1 + value2
    negative ? -sum : sum

struct ExampleControllerTest < ATH::Spec::APITestCase
  def test_add_positive : Nil
    self.get("/add/5/3").body.should eq "8"

  def test_add_negative : Nil
    self.get("/add/5/3?negative=true").body.should eq "-8"

# Run all test case tests.

Integration tests allow testing the full system, including event listeners, param converters, etc at once. These tests do not utilize an HTTP::Server which results in more performant specs.