Since the functionality this library provides is foundational—intended to be consumed by other libraries—there isn't really much in the way of public facing capabilities that could be usefully tested in a formal Quality Assurance (QA) process. If such a formal QA process were involved in this iteration, about the most that could be done would be to execute the unit test suite and verify that those tests execute without failures or errors.
Similarly, since the bulk of the stories involved in the iteration were for the benefit of developers, there would be little external acceptance needed; the fact that the various classes in the library exist and function as expected should be sufficient for acceptance of those stories:
- As a developer, I need a common definition and functional structure to represent addresses...