Is FIT Testing Useful?

A question came up yesterday as I was explaining the virtues of FIT to the development team (see my previous entry).

The question was “Is FIT testing actually valuable?” The argument being does FIT testing eliminate or reduce the need to do any other type of testing? I.e. would the addition of FIT tests decrease the need for GUI testing? The preliminary answer was maybe if the QA person believed the FIT test results. The main objection was that even if I use FIT to test the domain layer, I still need to test the interaction of the UI layer with the domain layer, thus testing the domain layer as a result. The addition of FIT just adds a maintenance burden to the QA team.

Based on that argument the only value FIT would add would be systems that do not have a UI, i.e. services.

1 Comment

  • > thus testing the domain layer as a result



    This domain layer is limited by the UI, where FIT would not. Useful if testers want an alternate arena to test (compare?) limits in there own creative (tabular?) space, but not if they're simply looking for system validation.



    I agree that FIT's an augment not a replacement.

Comments have been disabled for this content.