Page MenuHomePhabricator

[SQLite] implement tests for messages search
ClosedPublic

Authored by kamil on Jul 23 2024, 2:54 AM.
Tags
None
Referenced Files
F3358300: D12851.id42670.diff
Sun, Nov 24, 4:01 AM
F3358203: D12851.id42702.diff
Sun, Nov 24, 3:38 AM
F3358079: D12851.id42707.diff
Sun, Nov 24, 3:25 AM
F3357783: D12851.diff
Sun, Nov 24, 1:35 AM
F3352295: D12851.diff
Sat, Nov 23, 5:26 AM
Unknown Object (File)
Fri, Nov 15, 11:01 PM
Unknown Object (File)
Thu, Nov 14, 9:57 PM
Unknown Object (File)
Thu, Nov 14, 2:49 PM
Subscribers

Details

Summary

Testing searching logic - tests implemented by @inka.

Depends on D12850

Test Plan

Run tests

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Jul 23 2024, 5:03 AM

We can consider one more thing: sorting the returned messages.

web/shared-worker/queries/message-search.test.js
139–146 ↗(On Diff #42670)

Shouldn't this contain targetMessageID?

143 ↗(On Diff #42670)

Can we use constants from messageTypes?

152 ↗(On Diff #42670)

Can we validate more than just the ID? Like we do in other tests.

210 ↗(On Diff #42670)
232 ↗(On Diff #42670)
inka added inline comments.
web/shared-worker/queries/message-search.test.js
155 ↗(On Diff #42670)

Can we change the text to reflect that the timestamp can be equal?
For example "should return only messages with time equal or smaller than timestampCursor"

168 ↗(On Diff #42670)

Why is this a leave thread message?

277 ↗(On Diff #42670)

This is the same test as should prioritizes timestampCursor over messageIDCursor, we can remove one of them

This revision is now accepted and ready to land.Jul 23 2024, 6:44 AM