![]() Quite a bit of this can be attributed to not knowing anything. I figured a year would be sufficient to bring it to closure. Protip for backend engineers - CSS and SQL are equally important languages.Īfter deciding to take a few months off, I wanted to work on this project full-time. The final rewrite was the longest, but it layed the foundation for actually building a web application as I learnt CSS and wrote my first frontend code ever. 2019-11 - 30 days to Phoenix Liveview Before Liveview, I was using Drab.In this particular project, zrangebyscore was completely abused and a re-design reduced the storage from 3GB to 200MB, and SPA 2019-04 - 5 days to Elixir Maru, Redis On a side note, it’s actually quite incredible what you can build with Redis.2016-01 - 10 days to Elixir Plug, Redis, C++ search, SPA.2008-01 - Erlang, C++ search, and JQuery SPA.Essentially, I had been keeping it in a 32-bit container for years., so I started porting them. But over time the backend got more difficult to maintain The search was super-finicky to keep running, mostly because it could barely be compiled and had random memory issues on more modern distros when it even could be compiled. Having no frontend experience, I didn’t dare touch the frontend. and a single page frontend using jquery.an api server written in Erlang with C nifs. ![]() a 32-bit architecture search index written in C++.It consisted of several different services: P.S.Once upon a time there was a semi-useful hobby project that was handed to me to maintain. You and your team can guarantee comprehensive test coverage for your LiveView applications, ensuring that you move quickly while maintaining bug-free code. The powerful set of tools in your LiveView testing kit is just one of the many reasons that teams can be so productive in LiveView. This means you can easily test interactions between live views by relying on simple message passing. LiveView is built on top of OTP, and a live view is nothing more than a process. We can use the functions in the LiveViewTest module to apply the same three-step process that guides all of our tests, making it quick and easy to spin up tests for even complex LiveView interactions. This article showed that the LiveViewTest module provides all the functionality you need to exercise the full range of LiveView interactions in integration tests. You can even use the same elegant reducer pipelines in your tests to verify the behavior of your live view pipelines. This provided opportunities for deep unit testing to quickly cover lots of scenarios and edge cases. In the previous post, we comprised our individual live views from pipelines of single-purpose reducers. ![]() LiveView empowers you to write robust and comprehensive tests without a huge investment of engineering effort. Wrap Up: Write Robust and Comprehensive LiveView Tests Our three-step LiveView testing procedure neatly applies to both integration tests that exercise internal live view behavior, and tests that validate the interactions between live view processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |