In the last two blog posts, you learned that Ember treats testing as a first-class citizen. Out of the box, Ember provides 3 types of tests so that you can fine-tune test coverage and performance. It also supports a variety of addons and debugging tools to improve your developer experience in testing.
Today, we address an important question: How should you write tests? By the end of this post, you will learn 5 simple rules that I like to follow. The rules aren’t do-this-or-do-that’s (cold hard facts). Instead, they carry nuance and interesting side stories. To keep your learning experience fun, I will transcribe my talk at EmberFest 2019 (rather than summarizing it) to engage in a dialogue with you.
Continue reading “Write Tests Like a Mathematician: Part 3”
Ember provides 3 types of tests out of the box:
- Unit tests
- Rendering tests (previously known as integration tests)
- Application tests (previously known as acceptance tests)
Broadly speaking, these tests differ in two aspects:
- Which parts of your app they check for correctness. Having different types of tests help separate testing concerns.
- How fast they execute.
Let’s take a look at each type and when you might use one over another.
Continue reading “Write Tests Like a Mathematician: Part 2”
Ember gives you the power to write tests and be productive from day one. You can be confident that your app will be correct today and years from now. A question remains: How should you write tests?
Since tests are a core part of the Ember framework and your development cycle, I will dedicate several blog posts on best practices for writing tests, based on my experience at work and former life as mathematician.
Today, we will cover why testing is important, what tools can help you with testing, and how to run and debug your tests.
Please note that some tools may be readily available for Ember only. However, the best practices that I will mention should be independent of your framework. After all, tests are a universal language, just like math is.
Continue reading “Write Tests Like a Mathematician: Part 1”
The last part of this series is short. You can check out the Matlab code for implementing FEM today! I encourage you to see how the code demonstrates ideas that we studied. These include pullback to parent domain, Gauss quadrature for numerical integration, and postprocessing for visualization.
The geometries that we considered so far are simple. If we are to analyze a complex, real-world structure, we need a way to accurately model its geometry. Not to worry, we can map a simple element to a complex one using a function.
Today, we will study the isoparametric approach. It tells us how to define the function so that we can evaluate integrals fast and achieve optimal rate of convergence. It is key to making FEM practical and powerful.
Continue reading “Topics in Computational Mechanics: Part 4”
You must be logged in to post a comment.