📈
Using Ecto Test DSL
  • A demonstration that I hope convinces you to read on
  • What the library is for
  • What next?
  • The Ecto Classic Variant
    • The examples module
    • Describing an example (EctoClassic.Insert)
      • Params (including associations)
      • Changeset checks
      • Checking database constraint handling
      • Avoiding repetition in changeset checks
    • How EctoClassic.Update differs
  • Working with the tool
    • The Tester submodule
    • Customizing the changeset, insertion, and other functions
    • Functions to support regular (non-declarative) ExUnit tests
      • Special example-creation functions
    • Customizing the workflow
    • Useful functions
    • Tracing
    • TDD
    • Writing your own variant
  • How do I...?
    • Untitled
Powered by GitBook
On this page

Was this helpful?

What next?

PreviousWhat the library is forNextThe examples module

Last updated 4 years ago

Was this helpful?

You can find instructions for setting up the library at its . For tts_ecto_example, note that a server is started in and the file instructs the compiler to compile.ex files within thetest subdirectory. (Example files end in.ex.)

The library is built to be "pluggable", using variants. However, the first two variants come from a Phoenix/Ecto . Because of that, it makes more sense to explain the Ecto Classic variant (the simpler of the two) first, rather than start with an explanation that applies to any possible variant.

I haven't started extracting the second variant, the Ecto View Model variant, from the app's original version of this library.

Github page
test_helper.exs
mix.exs
app of mine