good point, thanks Abhilash!
Mike
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ:
On Thu, Jan 21, 2021, at 10:38 AM, baguazhan...@gmail.com wrote:
> Thanks Mark!
> We don't want to leave artifacts behind but want to see the testing
> data in the db before it wipes about. The goal is to see if we can
> write some data to another database.
The test suite doesn’t just wipe
Thanks Mark!
We don't want to leave artifacts behind but want to see the testing data in the
db before it wipes about. The goal is to see if we can write some data to
another database.
thanks!
Mike
___
Mailman-Developers mailing list --
On 1/3/21 7:51 PM, baguazhan...@gmail.com wrote:
> Thanks Mark for the answer!
> Now I'm able to use MAILMAN_EXTRA_TESTING_CFG=/tmp/mailman/sqilite.db
> python3 -m nose2 -v mailman.model.test
> and can see the file timestamp changed after I run unittest.
>
> but the sqlite database seems empty
Thanks Mark for the answer!
Now I'm able to use MAILMAN_EXTRA_TESTING_CFG=/tmp/mailman/sqilite.db python3
-m nose2 -v mailman.model.test
and can see the file timestamp changed after I run unittest.
but the sqlite database seems empty when I query tables like select * from
mailinglist;
I tried
On 1/3/21 5:22 PM, Mark Sapiro wrote:
>
> Tests run that way will use their own sqlite DB which is removed after
> testing. You can use any database you like by configuring it in a file
> containing a [database] section with appropriate class and url
> definitions and then doing something like
>
On 1/3/21 4:44 PM, baguazhan...@gmail.com wrote:
> Hello All,
>
> Happy New Year 2021!
> I've configured mailman using sqlite as backend database. but when I run
> unittests,
> e.g. python3 -m nose2 -v mailman.model.test
>
> seems the data is not write to production sqlite database, so which
