Every method in the adapter has built-in integration tests; however, only a small amount of intelligence was put into the process. It will use mock data and run standalone tests based on the mock data, but not much more.
- Integration tests often need to be executed in a specific order (i.e., create an item before retrieving or updating it, and lastly deleting it).
- Many integration tests depend upon data as required information that is needed to create an item.
- Often, creating one item may require the existence of another item.
- New integration tests generated by the Adapter Builder take these factors into consideration based on the information that is put into the adapter. In simple terms, “if it can figure it out, it does.” This provides additional time-to-value into the process to build and test a useful adapter.