> > > > 2- Is a formal distinction being made to functional testing and unit > > testing? > > Yes . Unit test cases are lightweight , run fast and the scope is > usually a single software "component" , whereas functional tests > require a whole Trac instance (server et al.) up and running and are > usually aimed at checking usability/interaction aspects . > > That makes sense. Is it correct then that for example our Travis CI integration only runs the tests it finds, thereby not making a distinction whether those are unit tests or functional tests?
> > > 4- How are generally databases initialised for testing purposes? > > > > There should be something in tests folder . Unit tests usually rely > upon mock objects or in-memory SQLite database and might be setup, > torn down every time for individual test cases , whereas functional > tests require connection to a DB engine (sqlite, postgresql, mysql, > ...) > > Ok. Is it true then that Trac testing does not rely on an automated regression test? In other words, all tests rely on a test-specific initial data set that can be tied back to issues that have in the meantime been resolved? Or put differently, there is no regression data set that has been developed purely for regression testing core Trac functionality? -- figaro -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
