You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've agreed that it makes sense to standardize reporting of workstation test results a bit, to ensure we consistently capture version and environmental data. For example:
host OS used for testing (Qubes vs. Linux/Mac; versions thereof)
server environment (dev/staging/prod)
workstation environment (dev/staging/prod)
client environment (e.g., sd-app vs. an sd-dev type setup)
commit hash; any applied patches
While automatic gathering of this data may help in future, for now let's just agree on a standard format to use & what information is most important to gather. See this report by Allie, for example: freedomofpress/securedrop-client#1025 (comment)
The text was updated successfully, but these errors were encountered:
We can always port it at some point, but I see value in using the test-results when reviewing PRs, as well, so wiki page as a first attempt definitely make sense.
We've agreed that it makes sense to standardize reporting of workstation test results a bit, to ensure we consistently capture version and environmental data. For example:
sd-app
vs. ansd-dev
type setup)While automatic gathering of this data may help in future, for now let's just agree on a standard format to use & what information is most important to gather. See this report by Allie, for example: freedomofpress/securedrop-client#1025 (comment)
The text was updated successfully, but these errors were encountered: