Commit 61b116a8 authored by Jérome Perrin's avatar Jérome Perrin

testUpgradeInstanceWithOldDataFs: rebuild with more bt

Procedure to update was:

1. edit bin/runUnitTest.real to change connection string to "erp5_test_0@erp5-catalog-0:2099 testuser_0 testpassword0"
2. in erp5.git repo, checkout at d8961c5195a214ec1257cfea55762360cba06b14
3. copy new testUpgradeInstanceWithOldDataFs.py in products/ERP5Type/tests
3. run test with --save, with full indexing activated:

    ./bin/runUnitTest --portal_id=erp5 --enable_full_indexing=portal_types,portal_property_sheets --save testUpgradeInstanceWithOldDataFs
4. copy files here
5. rewrite with rewrite_data_fs.py
6. rewrite the dump to keep compatibility with old mariadb (we might drop this at some point)

    sed -i -e s/utf8mb4/utf8/g dump.sql
parent 03af34ea
This source diff could not be displayed because it is too large. You can view the blob instead.
  • This commit message was wrong, sorry @rafael

    1. edit bin/runUnitTest.real to change connection string to "erp5_test_0@erp5-catalog-0:2099 testuser_0 testpassword0"

    should be instead:

    1. edit bin/runUnitTest.real to change connection string to "erp5_test_0@erp5-catalog-0:2099 testuser_0 testpassword0", with all the extra spaces so that this connection string matches exactly the one that rewrite_data_fs.py will replace.

    It's necessary to use a connection string of this exact length

  • I see, I think my mistake was not placing exactly the full lenght on the file.

    However, there are a second problem I notice, the fact that modifies the saved tests before run, breaks the next tests that would use --load option on the project.

    (I will return to fix up this for the next upgrade, as the problem seems now solved related to upgrades)

  • ah yes, probably this does not work with SavedTestSuite

Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment