{{Header}} {{Title|title= Testers Wanted! }} {{#seo: |description=Registered Testers Contribute to Stability |image=Testschecklist.png }} [[File:Testschecklist.png|thumb|250px]] {{intro| Registered Testers Contribute to Stability }} = Introduction = {{project_name_long}} needs more users to test new {{project_name_long}} package updates before those updates reach more users. Please [[contribute]] by becoming a registered tester. This is a volunteer task. {{Testers-only}} = Registered Testers = {{IntroLike| A registered tester is a volunteer who installs test updates on a test system, uses that system normally, and reports issues if something goes wrong. }} Why register? See [[Test#Rationale_for_Registration_of_Testers|Rationale for Registration of Testers]]. Advantage of being a (registered) tester? Higher impact on development. Avoid bugs entering the stable distribution breaking your workflows. {{box|text= * Short summary: Set up a test installation, enable a testing repository, create your initial registration thread, use the test system normally, install updates, reboot, and post short keep alive checkins in the same forum thread. }} How to become a registered tester? {{IconSet|h1|1}} '''Create a separate test installation.''' Create a separate {{project_name_short}} installation solely for testing. This keeps testing separate from your main stable system and reduces the risk of test updates affecting your everyday setup. Optional. If you are comfortable with revert or manual troubleshooting, a separate testers installation is optional. {{IconSet|h1|2}} '''Enable a testing repository.''' Enable the stable-proposed-updates or testers repository via the [[APT Repository#Change_{{project_name_short}}_APT_Repository|Derivative Repository Tool]]. A repository is the source your system uses to download updates. These two repositories provide updates that still need wider testing before broader rollout. {{IconSet|h1|3}} '''Create your initial registration thread.''' Create your forum thread so developers know that you are actively testing. * Use the full template: Use the full forum template below when creating your initial registration thread. * Purpose of the initial post: The initial forum post gives developers a quick overview of who is testing, on which platform, which repository is being used, which version is being tested, and how often checkins are expected. * Adjust the template: Note: Edit the following template to match your setup and plans. * No excessive formality: There is no need to worry about formatting details. If the title or content of the post is imperfect, developers may ask for clarification and/or correct typos. Example forum title: {{CodeSelect|code= [tester] - VirtualBox - version 18 - testers repository }} Example forum post content: {{CodeSelect|code= * platform used: VirtualBox, KVM, Qubes, ISO, distribution morphing * planned checkin frequency: weekly (Sunday) * repository used: testers * version used: 18 }} {{IconSet|h1|4}} '''Use the test system as a registered tester.''' * Continue regular use: After registration, continue using the test system for normal activities. Real day to day use helps uncover bugs that may not appear during limited or artificial testing. * One thread per major release: Major releases diverge quickly once a new one is released, so it is useful to know what releases are being tested. * Use a similar configuration: For example, if your stable repository installation disables autologin, also disable autologin in your testers installation. * Upgrade: Install updates when they become available. * Reboot: Restart after upgrades because some bugs only appear after reboot. * Stay informed: [[Stay_Tuned|Follow Kicksecure Developments]] and subscribe to news so you do not miss important updates, announcements, or testing requests. * Search before reporting bugs: Before reporting a bug, first search the relevant {{project_name_short}} forums and developer portals for the same issue. This helps avoid duplicate reports and may already provide a workaround or explanation. ([[Please_Use_Search_Engines_And_See_Documentation_First|Please Use Search Engines And See Documentation First]]) * Major release upgrade: When performing a [[Release Upgrade]], please create a new forum thread for the new release and post checkins for each release separately. * Indicate when leaving a thread: If you no longer wish to test a particular release, please leave a post mentioning this at the bottom of your tester thread for that release. {{IconSet|h1|5}} '''Post keep alive checkins.''' {{anchor|show=true|Registered Tester Keep Alive Checkins}} Stay active by posting regular checkins to confirm that you are still testing. Keep alive checkins can be short. You do not need to post the full template every time. * Post in the same thread: Later checkins can be brief status updates in the same thread unless important details changed. * Short checkins are enough: A short simple one sentence post such as: ** {{CodeSelect|inline=true|code=No issues found.}} ** {{CodeSelect|inline=true|code=Issues found and reported.}} ** {{CodeSelect|inline=true|code=No additional (non-duplicate, not yet reported) issues found.}} * Do not use your testers thread for bug reports: If you find an issue, please create a separate forum thread for that issue instead of posting the full bug report in your testers thread. * One issue per thread: Please follow the usual rule: 1 issue = 1 forum thread. * Update details when needed: If your platform, repository, version, or checkin frequency changed, mention that in your next checkin and edit your original post to reflect the changes. * Checkouts: If you cannot continue testing at any time, you can post a notification that you are signing out as a registered tester. * Inactivity or checkouts: In case of inactivity or checkouts your registered tester forum thread may be retitled, archived, moved to the trash bin, or deleted entirely. {{IconSet|h1|6}} '''Done.''' Your tester setup is complete, and ongoing testing can be tracked through short forum checkins. = Freedom Software = * Available to everyone: [[Reasons for Freedom Software|{{project_name_short}} is Freedom Software]] / Open Source. All [https://www.{{project_clearnet}}/#security existing] and [[#New Security Features Looking for Testers|new]] security features and underlying concepts are available free of charge for any purpose. * License terms still apply: Use is free of charge provided the respective license agreements are honored. {{project_name_short}} is [https://forums.whonix.org/t/lets-call-it-freedom-software-rather-than-free-software-or-open-source/6961 Freedom Software] [[Copyright#License|licensed]]. = New Security Features Looking for Testers = The following security features are already available in {{project_name_short}}, but they are still disabled by default. They need more real world testing before they can be enabled by default in a future {{project_name_short}} upgrade and release. The ordering below reflects developer views on their "production ready" status, from most to least ready. * none listed yet Archived. These features are already well tested enough and currently require add-on development work rather than more general testing. # [[Security-misc#Reduce_Kernel_Information_Leaks|Reduce Kernel Information Leaks]] → [https://forums.whonix.org/t/restrict-hardware-information-to-root-testers-wanted/8618 Restrict Hardware Information to Root - Testers Wanted!] # [[Security-misc#hidepid|hidepid]] # [[Security-misc#Remount_Secure|Remount Secure]] # [[Kernel|Install Newer Kernel Versions]] = Rationale for Registration of Testers = * Need for enough testers: {{project_name_short}} requires a large enough group of users to properly test planned updates. * Fewer undiscovered bugs: Otherwise, bugs might go undiscovered and be inadvertently introduced into the stable repository. * Privacy: {{project_name_short}} server does not have tracking. {{project_name_short}} developers do not know how many people use the stable, stable-proposed-updates, or testers repository. Related: [[Privacy|Privacy Goals and Non-Goals of Kicksecure]] ** No statistics on actual testing: Therefore, {{project_name_short}} developers do not know if testing has actually been performed. [[Stable Version User Experience]] https://forums.whonix.org/t/updating-broke-mouse/23114 = Limited Availability for Registered Testers Positions = * Limited availability: After a sufficient number of testers are active, formal registration may be (temporarily) closed. This helps conserve development time spent reviewing tester communications. You can still test, install updates, and report bugs without formal registration. = Additional Testing = The most active testers are recommended to: * Stay informed: [[Stay Tuned]] * Check the forum tag: Check the forum tag testers-wanted, see: [https://forums.{{project_clearnet}}/tag/testers-wanted testers-wanted forum tag] ** Confirm whether extra testing is still needed: If a {{project_name_short}} release is still tagged testers-wanted, first check if there is already a corresponding {{project_name_short}} stable release of that version. To find out, check [[Stay Tuned]]. If there is already a release of that version, then no extra testing is required anymore. That would mean removal of the testers-wanted forum tag was forgotten. = See Also = * Ways to contribute: [[contribute|Ways to Contribute]] * Website and server tests: [[Website_Tests|Website Tests / Server Tests]] = Footnotes = {{reflist|close=1}} {{Footer}} [[Category:Development]] [[Category:Design]] [[Category:Documentation]]