Add packaging tests link

[Imported from Trac: page NewbieDeveloperSetup, version 23]
amontero 2014-11-22 11:39:57 +00:00
parent 630b90fd07
commit 8aad947e84

@ -40,6 +40,6 @@ n. Help [reviewing patches](PatchReviewProcess). It is a good way to familiarize
o. Learn [how to submit patches](Patches) o. Learn [how to submit patches](Patches)
p. Dive into the code! See some [/pipermail/tahoe-dev/2012-May/007337.html tips for diving into Tahoe's source code] and follow the [coding standards](CodingStandards) when you're ready to code. p. Dive into the code! See some [tips for diving into Tahoe's source code](https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007337.html) and follow the [coding standards](CodingStandards) when you're ready to code.
q. Learn [how to write tests](HowToWriteTests). Patches and new code should pass the automated testing before being eligible to be merged (see [this comment](/tahoe-lafs/trac-2024-07-25/issues/7573)#comment:88). There is a [list of patches needing tests]query:status=!closed&keywords=~test-needed if you want to get your feet wet. q. Learn [how to write tests](HowToWriteTests). Patches and new code should pass the automated testing before being eligible to be merged (see [this comment](/tahoe-lafs/trac-2024-07-25/issues/7573)#comment:88). Even [packaging has tests](https://tahoe-lafs.org/pipermail/tahoe-dev/2014-November/009268.html). There is a [list of patches needing tests]query:status=!closed&keywords=~test-needed if you want to get your feet wet.