Apologies ... this android mail client can top post only.
Thinking about manually managing fixtures ...
The actual process starts with email notification of changes. That might be a few or a dozen or a hundred or more specific changes. They might be for one of a dozen or so different reference tables. Alternatively, there might be a completely updated set of data including consolidated changes.
If there are more than a couple of changes I write a script to read the source data from wherever (eg pdf, excel/csv or html page) and auto-update the table.
There's much more thinking to do if I'm going to extend those updates to test chemicals - which were categorised snapshots of a previous status once updates arrive!
Mike
--
(Unsigned mail from my phone)
-------- Original message --------
From: 'Ryan Nowakowski' via Django users <django-users@googlegroups.com>
Date: 11/10/23 12:44 (GMT+10:00)
To: django-users@googlegroups.com
Subject: Re: Reference data while testing - interesting
> On 8/10/2023 2:26 am, 'Ryan Nowakowski' via Django users wrote:
> As it happens, we currently have fewer than a dozen ("representative") test
> chemicals so it would be possible to manually manage the fixtures - but that
> is so quill and ink I won't consider it.
What would your process be for manually managing the fixtures? Perhaps
this can be automated? The reason that I'm pressing here is that there
are advantages to having a test setup with no external dependencies where
all of your test data is in source code management alongside your code.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/20231011014440.GA7415%40fattuba.com.
No comments:
Post a Comment