Christian wrote: > 1. What additional tests/kind of tests are needed for Saros (from > which would it benefit)?
We have too few unit tests, too few integration tests, only few system tests, and hardly any real stress tests or performance tests. Stability is important and still tends to be problematic, so I would say integration tests and stress tests are particularly useful. > 2. Which areas are especially prone to bugs and not tested enough? When editing operations mix with "special" operations, such as - inviting further session members - sharing further directories - renaming files - creating or deleting files These are the most complex parts of Saros not only in terms of the actual program logic but also conceptually. https://www.saros-project.org/architectureDocumentation > 3. Which parts of the code are difficult to test so that there are too > few tests covering them? > 4. For which parts do enough test cases already exist? Are you aware of the Cobertura report? http://saros-con.imp.fu-berlin.de/jenkins/view/Build/job/Saros/1315/cobertur a/ Lutz ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
