So at a minimum, developers can know not to call TestOnly methods and at a maximum, test methods are not deployed in production builds. The first thoughts I have had are either use naming. I understand that this is generally considered bad practice in "TDD Utopia" but realistically, how have you dealt with this kind of conflict? if I were to add methods specifically for the test department. requirement for deletion (but one which conflicts with business user stories) (and may have delete pending on the backlog). The problem is, some of the Entity Repositories do not have delete methods as there has been no business requirement expressed for these yet. However, recently our test department has started running integration tests, and understandably they want to use our (already passing) business logic code to set up and tear down test state (rather than having to deal directly with a database) as they are mainly concerned with testing via the UI of the application and do not want to spend all day wrangling databases. behavioral specifications (Given/When/Then style) derived from business requirements, unit tests that reflect these and code that reflects the requirements of tests. We use a BDD/TDD sytle methodology for building our software (quite a large/complex application) The end result is. Looking for some practical advice here and any experiences people have had in a similar situation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |