Thursday, November 7, 2013

Integration Testing

After a few days of trying to get JUnit up and running, I have decided that integration testing will be the best route to take.  The way we ended up doing integration testing is to have a separate program which can invoke different elements and modules that we have create for this program.

Unit testing ended up not working to well as our classes often are reliant on many different services which may or may not be present.  Other obstacles with unit testing were that we were forced to test with junit 3 and the framework needed to run on a special application on the printer in order to see test results.  All of this made it unnecessary and clearly the wrong approach for testing.

In our test program, we take out individual classes and test them similar to how we would do unit testing but with more emphasis on how it will interact with the overall system.  For example with the EmailPrompt.java class we test that it can show all messages which are passed into the constructor in the radio list on screen.  We also test that the prompt returns the correct message by allowing the user in the program to test edge cases and off by one errors.

1 comment:

  1. Hello Zackary,
    The Article on Integration Testing with Brief Information about it .Thanks for Sharing about it. is informative. It gives detailed information about it .Thanks for Sharing the information on Integration testing. Software Testing Services

    ReplyDelete