On 24 March 2013 17:03, Ricardo Fabiano de Andrade <[email protected]> wrote: > And once soci's unit tests are in single cpp file this solution sounds > perfect Ott.
Currently, we build one testing program per backend. If we want, we can change it for use of a testing toolkit. For example, we may decide to: - build common tests separately as single program common for all backends, which execution will be configurable (i.e. list of backends and connection strings passed as command line arguments); - build backend-specific tests build as separate one per backend. Also, if we manage to write unit tests (for core) based on mocking, then that will become a separate program too. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
