From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 5E3936DE19DF for ; Sun, 25 Mar 2018 11:22:10 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PzkZs79g_CtL for ; Sun, 25 Mar 2018 11:22:09 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 562AC6DE2AD5 for ; Sun, 25 Mar 2018 11:22:07 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1f09dM-00056b-EL; Sun, 25 Mar 2018 13:40:44 -0400 Received: (nullmailer pid 18087 invoked by uid 1000); Sun, 25 Mar 2018 17:40:43 -0000 From: David Bremner To: Justus Winter , Floris Bruynooghe , David Bremner , "W. Trevor King" Cc: notmuch@notmuchmail.org Subject: pytest integration for the notmuch test suite Date: Sun, 25 Mar 2018 14:40:31 -0300 Message-Id: <20180325174034.17912-1-david@tethera.net> X-Mailer: git-send-email 2.16.2 In-Reply-To: <87po3x4tuc.fsf@thinkbox.jade-hamburg.de> References: <87po3x4tuc.fsf@thinkbox.jade-hamburg.de> X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 18:22:10 -0000 Here's one approach. A given pytest "file" can be embedded in a normal (for us) test script. As I write this, it occurs to me you might be thinking of embedding unit tests in the bindings source files; that would be easy to add, something along the lines of test_begin_subtest "python bindings embedded unit tests" test_expect_success "${NOTMUCH_PYTEST} ${NOTMUCH_SRCDIR}/bindings/python/notmuch" You could also run one source file of tests with test_begin_subtest "python bindings foo tests" test_expect_success "${NOTMUCH_PYTEST} ${NOTMUCH_SRCDIR}/bindings/python/notmuch/test_foo.py" that would give a less granular result, at the cost of more boilerplate