Browse by Tags
All Tags »
Automation Stac... »
Testing (RSS)
How much of your testing do you automate? How do you know whether you have automated enough - or too much? My current team is taking the Automate Everything approach. This means we automate every last test case. "110% automation", as one of our executives
Read More...
I tech screened a tester this morning for a position on my team. I always ask the candidate to describe the tester mentality. I loved today's interviewee's answer: More than the product working perfectly without any crash assert, if it is not intuitive
Read More...
Recently one of my teammates was showing off a WPF application he had built. Since it's easy to do, she built a Logical Functional Model and used it to script her demo. One of the cool things her app supported was reskinning (including rearranging and
Read More...
Dr. Dobb's published my article " Achieve More Comprehensive Verification With Less Work " online - check it out!
Read More...
Jerrad is writing a Logical Functional Model for a website. He is approaching the problem exactly right: figure out what the user actions are, and then organize them into a user-sane order. His example is all about searching, so the LFM could be very
Read More...
Your Logical Functional Model lets you write test cases from your user's point of view, test cases that focus on what is being done rather than how it is being done. Your Physical Object Model lets your test cases ignore the details behind interacting
Read More...
My previous post hinted that the Physical Object Model takes advantage of some underlying magic that makes different types of controls look similar. This "smudging" of controls into similarity comes courtesy of the controls abstraction layer. While each
Read More...
With the LFM defined and hooked up to Execution Behaviors it makes sense to move on to defining the Physical Object Model . The POM is often the simplest part because it's just a straightforward API around the user interface. Given Surveyor's UI: a likely
Read More...
Once you create your Logical Functional Model the other pieces can follow in any order immediately as chunks of your feature and LFM are defined. I'll follow the most typical pattern here, which brings us to Execution Behaviors. When you first define
Read More...
As soon as you have even a vague idea about what your feature is all about you can start defining your Logical Functional Model. Ideally your entire feature team will take part in this exercise, but you can certainly do it on your own as well. Ask yourself
Read More...
All that theory is great, but without a practical application none of it matters. Thus Surveyor. Surveyor is a simple application for creating online surveys. The UI will look something like this: You have three sets of questions: those you have yet to
Read More...
Factoring these details out of the test case into intuitively organized libraries allows the test case to focus on the essence of what it is testing rather than incidental details. This helps us write more comprehensive tests faster but spend less time
Read More...
Most test cases that manipulate a user interface are tightly tied to the current details of that UI. What the test case is doing often gets lost in the details of how it is doing it. We abstract away these implementation details by wrapping our application
Read More...
Details regarding how data is pulled out of our application’s internal data structures and other parts of the system environment are factored into an Application Internals model. This isolates knowledge about where data is found and how it is accessed
Read More...
Verifying that a test case’s actions had the expected result is perhaps the most important part of testing. Every test case does something at least a little differently than every other test case, so the expected results are often a little different.
Read More...
