Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test for syncing complex forms twice #1256

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

rmunn
Copy link
Contributor

@rmunn rmunn commented Nov 19, 2024

WIP. Will fix #1251 when completed.

So far this has a test that reveals a bug in the seed data for the CRDT sync tests, and another test that's an attempt at replicating what happens when sena-3 is synced twice in a unit test. (Though the second test, which should be failing, is passing right now so it's not yet a reproduction). I may give up on reproducing this in a unit test, and just write an integration test that syncs sena-3 as described in #1251 (comment).

The second sync, that should do nothing, was importing the seed data,
including the parts of speech and semantic domains that weren't in
fwdata after the first sync.
@rmunn rmunn self-assigned this Nov 19, 2024
This was not successful at reproducing the issue we encounter syncing
sena-3, because this test is passing. I'll keep working at it.
@myieye
Copy link
Contributor

myieye commented Nov 19, 2024

I just synced elawa multiple times and each time the number of fwdata changes decreased, but it took about 5 syncs before it was 0.
So, I think it's probably a good idea to have an integration test that uses a project with all out model features to ensure that a second sync always results in 0 changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Trying to sync sena 3 twice via fw headless results in an error
2 participants