![]() The idea behind System Under Test is that every test we write should be focused on verifying the behavior of some piece of our software, whether it's a function, a component, or something else. There's even a term for this: it's called System Under Test, which is sometimes abbreviated as SUT. ![]() Now, "what it is we're trying to test" is of critical importance when it comes to identifying these abstraction layers. But fillIn is an abstraction around this low-level code that's designed from the perspective of a user actually using our app - and because of this we would say that fillIn is a more expressive way to represent what it is we're trying to test. This is pseudocode but you get the idea - this is lower-level because it's using these lower-level APIs to interact with our web app, in the same way that a programmer would in code. So what does that mean? Well let's take a look at a test. So the idea here is that, all the code within our test suite is at a certain abstraction level, and it's up to us to ensure that any code within a single test is all at the same consistent level pf abstraction all the way through. Something that had a big impact on how I write tests was learning about levels of abstraction in testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |