About Testing

this page explains the structure of the testing sub project, provides links to public testing resources, and describes how to contribute to the sub project the testing sub project covers checks for rk3576 based boards used in flipper one development its goal is to turn each device feature into a repeatable test with a clear result testing currently prioritizes hardware verification, but test notes and assets can also cover user interface or sound checks when those areas need repeatable pass/fail criteria the testing sub project consists of ✅ task tracker https //github com/orgs/flipperdevices/projects/14 📚 manual test descriptions docid\ rvvadwks7cxz 5srk9zm0 📁 automated test scripts https //github com/flipperdevices/flipperone testing ✅ task tracker the public testing project board https //github com/orgs/flipperdevices/projects/14 tracks open work for the testing sub project there, you can see what the team is working on, follow progress, and find tasks that need community help some tasks are open to the community and marked with a help wanted label you’re welcome to join the discussion on these tasks or submit test results when a task asks for them 📚 manual test descriptions the testing docs explain what should be checked for each subsystem these pages are meant to complement the scripts the docs describe the test goal, setup, expected result, and known gaps, while the repository contains runnable scripts or assets when they are available docs in this section follow the same order as the navigation general docid\ n 5trbykrbqtoi7cc8zxz boot targets, test images, and common setup notes power docid\ pv90ncbsmczf1cwjjnq1y power management testing notes graphics docid\ uhhept9l5nyhqu7a 2fwu gpu, hdmi, usb c displayport, and no graphics boot target checks video decoding docid\ flpizny93ntenimcwbz3x video decoding checks under graphics testing network docid\ juxalflkc mzkcynieiri wi fi and bluetooth test scenarios expansion modules (m 2) docid 366net2xmvthalqmbjd m 2 expansion module test notes cellular modems docid\ c5 w3wocshrwmihfh3aap cellular modem tests for m 2 modules hardware verification at this stage, testing is mainly used to verify whether each hardware component performs its intended function a good test should answer a narrow question, for example does the interface come up? does the expected device appear in linux? does the measured value stay inside the expected range? does the output match the selected boot target? each test should end with a clear yes/no or pass/fail result when a result is not clear, document the exact observation and mark the open question instead of hiding it behind a vague pass test bench todo describe publicly available test setup 📁 automated test scripts the public flipperone testing https //github com/flipperdevices/flipperone testing repository contains scripts and test assets for rk3576 based boards it includes a shared test runner, module directories for major subsystems, and a results/ directory layout for generated reports to avoid duplicating a fast changing list of implemented tests here, use the repository readme https //github com/flipperdevices/flipperone testing/blob/dev/readme md as the current index of available automated checks, supported modules, and report formats how to contribute the testing sub project accepts contributions in three forms comments on open task docid\ rvvadwks7cxz 5srk9zm0 with ideas, suggestions, and improvements testing and uploading test results docid\ rvvadwks7cxz 5srk9zm0 to open testing tasks pull requests for test improvements docid\ rvvadwks7cxz 5srk9zm0 ‎ comment on an open task if you have an idea on how to improve a test, add missing setup details, or clarify expected results, comment on a relevant task in the testing project board https //github com/orgs/flipperdevices/projects/14 ⚠️ contributions only — no flooding to keep collaboration productive, please keep comments on topic open tasks are for contribution related discussion only if you have an idea or concern, first turn it into a concrete contribution and share it as a comment on a task for general questions or discussions, you're always welcome to join the conversation on social media https //x com/flipper rnd or discord https //discord com/invite/flipper ! contribute a comment on an open task if you have an idea on how to improve a test, add missing setup details, clarify expected results, or share a test report, comment on a help wanted task in the testing project board https //github com/orgs/flipperdevices/projects/14 pick a task in the testing github project https //github com/orgs/flipperdevices/projects/14 , browse the open tasks and click the one labeled help wanted that you want to contribute to write your suggestion or report in the comments section, clearly describe your contribution and, if helpful, attach screenshots, videos, code snippets, logs, result files, or links to a draft pull request attachment size limit images 10 mb videos 100 mb click comment to submit we review all comments carefully! we may ask additional questions about your idea in the task thread, so please watch for github notifications in your email ‎ test and report the results testing tasks are published in the task tracker https //github com/orgs/flipperdevices/projects/14 with the help wanted label each testing task contains all essential testing requirements, as well as the expected format for submitting a test report review the testing requirements and perform the test attach your test report as a comment in the task thread ‎ contribute via a pull request contribute via a pull request contributing via pull requests allows anyone to propose changes to the automated test scripts in the flipperone testing https //github com/flipperdevices/flipperone testing repository on to manual test descriptions in the flipperone docs https //github com/flipperdevices/flipperone docs repository fork and clone the repository ( flipperone testing https //github com/flipperdevices/flipperone testing for changing testing scripts or flipperone docs https //github com/flipperdevices/flipperone docs for changing manual test descriptions) make your changes in the cloned repository open a pull request to the repository we review all pull requests carefully! we may ask additional questions in the pr thread, so please watch for github notifications in your email