Kaladaran/briar
0
0
Fork 0
mirror of https://code.briarproject.org/briar/briar.git synced 2026-02-11 18:29:05 +01:00
Code Issues Projects Releases Wiki Activity
Page: notes on testing
Pages
A Quick Overview of the Protocol Stack Adding support for new architectures in Tor Android Accessibility Android Power Management BDF BSP BTP Blog Client Blog Sharing Client Client API Notes Connect at a distance Create Account Design options for multi block messages Development schedule for private message deletion FAQ Field Guide Forum Client Forum Sharing Client Forums Fundamental Problems How Briar Connects to Contacts Introduction Client Mailbox Architecture Mailbox Properties Client Mailbox Scenarios Mailbox cannot reach Briar Messaging Client Navigate away from sharing screen Private Group Client Private Group Sharing Client Profile pictures Quick Start Guide RPC Notes Release Test Plan Roadmap Self destructing messages tests Software bill of materials for private message deletion Sponsor 1 Testing Translation Workflow Transport Key Agreement Client Transport Properties Client add already added contact at distance add contact after time out add contact at distance one contact offline add contact on biar received via hotspot add contact whilst pending contacts add nearby contact bluetooth off add nearby contact that was already added at distance add nearby contact then reconnect via BT add nearby contact twice app in background while do not kill me fragment displayed application lifecycle autostart mailbox on reboot when mailbox set up not completed yet autostart mailbox on reboot when mailbox set up blogs bluetooth setup screen briar connections opens from device view app settings briar in background during sharing briar mailbox test coverage briar mailbox tests executed cancel setup changelog code style comparative test several devices location and wifi settings connect multiple devices to hotspot connect with nearby contact create account on shared briar app delete and recreate contact at distance delete recreate nearby contact deny briar access to location many times deny briar access to location development 101 development workflow device offline warning devices tested disappearing messages sent to direct contacts download app scan QR code download type address manually error handling mailbox uploads feature workflow first install do not kill me fragment fresh install add contact distance reconnect via BT fresh install add nearby contact BT reconnect BT home import somebody elses messages install first time interrupt scanning qr code interrupt unlinking from briar side introductions multiple contacts disapp msgs on off invite multiple contacts to private group location off during contact creation mailbox in briar settings mailbox is running mailbox no internet mailbox not reachable mailbox notifications mailbox onboarding screens scan QR Code mailbox onboarding screens share link mailbox strings translations mailbox success screen mailbox system clock in the future mailbox system clock in the past mailbox test coverage mailbox wiping complete screen main activity reset everything to initial state make intro dis msgs on autodecline make introductions disappearing messages on intro accepted make introductions disappearing messages on intro declined by both make introductions disappearing messages on intro declined by one make introductions disappearing messages on make introductions disappearing messages onoff intro accepted make introductions disappearing messages onoff intro decl autodecl by both manually change battery optimisation setting to ON manually change battery optimisation setting to off message upload both x and y have mailboxes messages as expected no mailbox messages removable media mailbox messages uploaded Y knows x has mb messages uploaded to mailbox correctly mialbox not reachable nearby contact no mailbox autostart on reboot when QRcode scan canceled no mailbox autostart on reboot when mailbox stopped by user notes on testing notification mailbox unreachable disappears after tapping notification mailbox unreachable disappears when mailbox reachable notification mailbox unreachable disappears when mailbox unlinked notification mailbox unreachable onboarding UI open battery settings open hotspot manually open hotspot scan qr code permissions pre review checklist private group invitations messages product backlog re add deleted contact reconnect via BT reboot briar device after QR code scan receive messages during contact creation reconnect via BT when BT = OFF reconnect via BT when Briar BT OFF and device BT OFF device location OFF Briar no access to location reconnect via BT when Briar BT OFF and device BT OFF device location OFF reconnect via BT when Briar BT OFF and device BT OFF reconnect via BT reimport imported messages remove nearby devices permissions and start app reopen mailbox after device goes to sleep restart mailbox after wiping do not keep activities rotate screen whilst adding contact at distance scan incorrect qr code scan qr code scan valid QR code more than once self destructing messages share app briar access to location OFF share app device location OFF share app device wifi OFF share app offline share app wifi in briar OFF signed commits stop mailbox stop sharing after download stop sharing before download finished threat model time last connected tor build process tor port transfer blog posts transfer direct messages transfer forum posts transfer introductions transfer messages with images unlink from briar side mailbox already unlinked unlink from briar side mailbox offline unlink from briar side unlink mailbox side when briar offline unlink mailbox side when briar online unlink mailbox upload new contacts to mailbox user allows connections and rotates screen user allows connections user leaves setup
Clone
18
notes on testing
Ivana edited this page 2022-04-10 10:51:59 +00:00

  • test Mailbox screens when user selects large font

  • test Mailbox screens on different screen types/sizes/ratios, portrait and landscape, all devices. This is a 'nice to have', as the cosmetics for different screens can be dealt with at a later stage and not necessarily in the MVP.

  • according to the mattermost discussion of 13/14 dec, there may be variations of illustration size used on mailbox screens - normal, short and none... if that decision is made, then that will need to be tested too

  • discussion on the MM 20/12 - error handling. Find out how to trigger each error response mentioned, to verify that they are handled correctly. Maibox_coverage_matrix.ods

  • https://code.briarproject.org/briar/briar/-/issues/2191 will give rise to a few scenarios

  • https://code.briarproject.org/briar/briar/-/issues/2226 also some scenarios when uploads do not complete successfully

  • verify that the messages are not sent to mailbox (own or contact's when contact is online - done

  • various scenarios of who is online and offline and what happens to messages in each case - done

  • find out what needs to be tested re:Tor.

  • to test what happens when different api versions are present in own and ocntact's mailbox or briar app... see discussion on MM,channel, today 4/4/22

"one possibility here, which i haven't fully thought through, is to use the existing client versioning mechanism to signal our support for mailbox versions. so api version 0.0 would be tied to mailbox properties client version 0.0, etc. api version 0.x would be backward compatible with 0.0, and 1.x would break compatibility with 0.x

so by looking at the client versions received from each contact we could work out whether the contact would be able to communicate with our mailbox, and if the contact sent us properties (in one or more of the major versions we support, since each major client version has its own independent group for exchanging properties) we'd know that we could communicate with that mailbox using the major api version corresponding to the major client version and the minor api version corresponding to min(our minor client version, contact's minor client version)

but all of this could also be done by including our own client and server api versions in our mailbox properties, or in a second type of update message exchanged by the mailbox properties client, and in that case it wouldn't be tied to the client version. which is maybe more sensible?

12:31 PM

(by client and server api versions, i mean the versions our briar app can speak as a client, and the versions our mailbox app can speak as a server. we need to send both if we want a contact to know whether we'll be able to talk to their mailbox)"

  • see discussiojn on MM on Friday 01/04/22 - that will likely need to be tested too. I wonder how we can make the user aware of a problem with their mailbox that requires their attention, like if it has been unreachable for too long.

Show a nagging snackbar in the main activity?

Show a button or icon in the nav drawer?

Use a system notification?

5:56 PM

A dialog that pops into the user's face?

  • uninstall briar without unlinking with mailbox, and uninstall mailbox without first unlinking to briar. The reinstall briar and try to link with the same mailbox instance s before, or reinstall mailbox and try to link with the same instance of briar as before.
  • try to link briar to one instance of mailbox, then unlink, and link with another. same for mailbox side - unlink from one instance of briar and link with another?
  • does it matter in which language briar is?

Back to Testing