Re: Regression test best/common practices

I've been testing my importers using : ``` from beancount.ingest import regression_pytest as regtest ``` And then letting pytest --generate the support files from the given input PDFs (in my case). For plug

Re: Regression test best/common practices

Please correct me if I'm wrong, but I don't think I can do that and still use fava and smart_importer. On Monday, January 10, 2022 at 12:14:35 AM UTC-6 bl...@furius.ca wrote: > On Mon, Jan 10, 2022 at 12:54 AM David Richey wrote: > >> I'm not entirely sure if I'm able to use beangulp since I'm

Re: Regression test best/common practices

On Mon, Jan 10, 2022 at 12:54 AM David Richey wrote: > I'm not entirely sure if I'm able to use beangulp since I'm using > beancount v2. Everything I've read indicates that beancount v3 is not ready > for use. Create a second setup with v3 just to run beangulp. v3 is working today (that's all I

Re: Regression test best/common practices

I'm not entirely sure if I'm able to use beangulp since I'm using beancount v2. Everything I've read indicates that beancount v3 is not ready for use. Even so, based on my understanding of the two tools (beangulp and the v2 import tooling), it's not clear to me how beangulp improves on the old

Re: Regression test best/common practices

Short answer: Use beangulp. Each importer can be invoked directly, with "identify", "extract", "archive" commands, but also "test" and "generate" commands. Write a driver script that will find all of the files you'd like to test and invoke your importer implementation (just the one .py file) on eac

Regression test best/common practices

Hello, I'm trying to set up regression tests for my importers, and I'm wondering about how people tend to do this (beyond the basic setup described in the docs). Specifically, would it be wrong to want to regression test all of my imported documents? If not, do you manually copy all of them fr