Ganga testing policy

Please read with care and apply smile

By default every bug has a test case in the testing framework

If you as an internal developer find a bug you are well placed to write the test case straight away. Make sure that it actually fails. The test-cases for bugs are in Ganga/test/Bugs

For new features there should be unit tests

For new features there should be Unit tests (so a test that depends on a minimal number of other things. The tests should check both that correct usage works but also that incorrect usage (like giving a non-existent filename for an options file) fails in the expected way.

For use cases there should be system/integration tests

For the more general LHCb use cases we should write system tests. These will confirm that we have actually implemented the requested behaviour.

-- JakubMoscicki - 18-Feb-2011

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2011-02-18 - JakubMoscicki
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ArdaGrid All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback