Exploring Extreme Programming
In our final article in the series on testing graphics, we’ll look at testing internal objects (rather than testing at the display level). We’ll look at several decisions around testing.
Screen-Based Tests: Two Extremes Screen-based tests focus on what’s visible rather than internal representations. We’ll consider two extremes for testing screen-based output: fully manual and fully automated. Then we’ll look at moves that can help you evolve from one to Continue reading Screen-Based Tests: Testing Graphics, Part 3
In Part 1, we discussed models for graphics. As we move into testing, let’s start with the visible part: the display.
Many applications work with graphics; applications with graphical user interfaces can’t escape them. We’ll look at several models for graphics, and in later articles explore how to test them.
People who unit-test, even many who unit-test in Extreme Programming, don’t necessarily test the user interface. You can use JUnit to assist in this testing, however. This paper will work through a small but plausible example, giving the flavor of testing and programming using JUnit. This paper is part 2, but can be read on its own; part 1 developed the model. Continue reading The Test/Code Cycle in XP, Part 2: GUI