On 5/27/16, figaro <[email protected]> wrote: > [...] > > 1- Where do the test cases originate from? Is it only the cases where the > developer has cared to add unit tests to his/her patch?
Patches , new features , API changes , ... in theory every new functionality deserves a (few) test(s) , at least to track regressions . > Does that mean that > those tickets marked as resolved (non-duplicate) and do not have unit tests > added are not tested? > Might be an indicator , but not necessarily has to the case . > 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 . > 3- Is it fair to say that the majority of the unit tests cover testing of > the graphical user interface of Trac and less so the APIs? All the opposite . > 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, ...) [...] -- Regards, Olemis - @olemislc Apache™ Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Brython committer http://brython.info http://github.com/brython-dev/brython Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- 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.
