api_weather

Gain insights into unit testing Elixir applications with ExUnit, explore advanced integration and E2E testing, and master OTP, Phoenix frameworks, API testing, and platform-specific refactoring.

testingElixir.tar.gz

First Test

SoggyWaffle-mix test

chapter2-RealExternalDependency - soggy_waffle_test

Chapter3- GenServer-Example

chapter1-isolating code 

chapter1-dependencyinjection -fine

Ch4-testing-ecto-schemas-

Ch4-testing-ecto-schemas--mix deps

Ch4-testing-ecto-schemas--Database tmux 2 shell makeup

Ch4-testing-ecto-schemas--Database tmux 2 shell window

Ch4-testing-ecto-schemas--Database tmux 2 shell databasetest

Ch4-testing-ecto-schemas--Database tmux 2 shell databasetest-copy

Ch6-testingPhoenix-error test

chapter2-RealExternalDependency - soggy_waffle_test-copy

Chapter3- GenServer-Example-copy

Ch6-testingPhoenix-error test-copy

Ch6-testingPhoenix-error test-copy-lbr

ch7-property-based-testing

Ch6-testingPhoenix-error test-copy-check

Ch6-testingPhoenix-error test-copy-happytest

Chapter3-edit

chapter1_l2

chapter1_l6

chapter1_l7

chapter1_l10

chapter1_l13

chapter1_l14

chapter2_l3

chapter2_l4

chapter2_l6

chapter2_l7

chapter2_l9

chapter2_l14

chapter2_l15

chapter2_l16

Ch4-testing-ecto-schemas--mix deps-refactor

Ch4-testing-ecto-schemas--mix deps-shared

chapter3_l4

chapter3_l5

chapter3_l6

chapter4_l3

chapter4_l4

chapter4_l5

chapter4_l6

chapter4_l7

test

chapter4_l11

chapter4_l12

chapter4_l13

chapter5_l3

chapter5_l4

chapter5_l5

chapter5_l6

chapter6_l4

chapter6_l5

chapter6_l6

chapter6_l7

chapter6_l9

chapter6_l10

chapter6_l11

chapter4_l13-copy

chapter6_l3

Ch6-testingPhoenix-error test-copywithMix

ch7-property-based-testing-copy

ch7_Introducing_stream_data

ch7_Writing Properties

ch7_Shrinking

ch7_Strategies

ch7_ Smoke

Chapter3- GenServer-isolating

Chapter3- Controlling

Chapter3- GenServer1

chapter4_l10

chapter6_l3-copy

ch7_ Properties

Testing is an essential part of the software development life cycle. A good automated testing suite streamlines feedback, allowing rapid creation and tight control over specific application components.

This course is a comprehensive introduction to testing Elixir applications with ExUnit. You’ll start with a review of unit testing principles before diving into writing tests with the ExUnit. You’ll build a comprehensive suite of unit tests before moving on to more advanced testing, including integration, end-to-end, and property-baste testing. In addition to the core Elixir environment, you’ll also develop tests for OTP, the Phoenix web framework, including JSON APIs and Ecto schematics. You’ll also explore refactoring for different platforms, server rendering, and design strategies.

By the end of this course, you’ll be an expert in unit testing Elixir applications with ExUnit and ready to build robust, performant applications using Phoenix.

Ensuring Elixir Application Performance with Testing and ExUnit

## Adding randomness to tests
We can solve some of the problems that example-based tests suffer from by introducing a bit of chaos in our tests. Using randomness to generate inputs will allow us to test a wider range of inputs against our code and potentially create inputs that trigger edge cases.

In our sorting example, what we really want to test is that the output of `Enum.sort/1` is a sorted version of the input. For any random input, we can think of a few properties that the output will always retain. For example, 
1) The output list always has the same length as the input list. 
2) Another property is that the output list is always sorted, which is something that we can check in a pretty straightforward way by checking that each element is smaller than or equal to the following one. 




Now that we’ve thought of these properties, we could change our test so that we generate random lists and test these properties on the output of our code instead of checking _what_ the output is. Let’s see how to do that with `property_based_testing/sorting/test/randomized_sort_test.exs` given below:

# Adding randomness to tests
We can solve some of the problems that example-based tests suffer from by introducing a bit of chaos in our tests. Using randomness to generate inputs will allow us to test a wider range of inputs against our code and potentially create inputs that trigger edge cases.

In our sorting example, what we really want to test is that the output of `Enum.sort/1` is a sorted version of the input. For any random input, we can think of a few properties that the output will always retain. For example, 
1) The output list always has the same length as the input list. 
2) Another property is that the output list is always sorted, which is something that we can check in a pretty straightforward way by checking that each element is smaller than or equal to the following one. 




Get to know the benefits of randomness in property-based testing

Randomness and Property-Based Testing

Getting Started

Unit Tests

Integration and End-to-End Tests

Testing OTP

Testing Ecto Schemas

Testing Ecto Queries

Testing Phoenix

Property-Based Testing

Randomness and Property-Based Testing