Tests Are Lame but they don’t have to be Ever since i started working with CircleCi at Sauce it bothered me that we don’t use what it has to offer to the fullest and this is especially so with tests circleCi has this really neat way of showing test results as shown below despite how nice doing this looks it also has another really useful feature it allows you to do splitting and parallelism on jobs this means jobs but specifically, a test can be split across say 4 machines and split up by the time it took to run the tests.
This one’s going to be really quick:
We have a list and we want to split it into 2 sublists based on some condition, to work on each of them separately.
LiveView provides real-time user interaction within an application. Some use cases where LiveView fit excellently in an application are input validation, button click, autocomplete and live search.
There are times when we need to do multiple operations at once on various database tables. For example, when creating a new entity, such as a user, we might want to also insert a related property in some other table, such as a table that holds the preferences of a user.
Looping through template variables The standard way to iterate through lists in Phoenix templates is to use for/1
<%= for post <- @posts do %> <%= render "post.
CircleCI Images CircleCI provides quite a few convenience images in order to speed up the build process. These are generally fairly robust images that will cover most cases.
CircleCI is a really useful tool for ensuring that your builds go through correctly, that all the libraries and dependencies are accessible and compatible when building clean, and so on.