Question thread #28

[pauamma]

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Comments

[quartzpebble]

What's DW's approach to automated testing? I see that there are tests in dw-free/t/. Does each test file correspond to a function? A module? Are there conventions we use? Where do I start if I want to add tests? Are there any recommended resources for writing tests in Perl?

I ask because I've been learning about writing tests for other projects I've been working on (in Python) and I'm working on this bug: https://github.com/dreamwidth/dw-free/issues/659 and planning to pick up some more, and I like tests that tell me I haven't broken things.

[denise]

The test coverage is spotty, and we don't make "run the tests" part of pre-pull-request testing because running them can corrupt the DB on your development machine. There's been some work done on it, but not a whole lot, so anything you wanted to do would be awesome!

[(Anonymous)]

"Want to do things with that", yes, "currently have the knowledge to", no. So, general question--any good testing-in-Perl resources?

[quartzpebble]

Whoops, that was me.

[denise]

I don't know much about it myself, but a quick Google search turns up this as a start. (I believe we do use Test::More.)