Searched full:plan (Results 1 – 25 of 44) sorted by relevance
12
| /Zephyr-latest/scripts/footprint/ |
| D | pack_as_twister.py | 30 from the plan.txt columns including an additional (last) one whth explicit
95 parser.add_argument('-p', '--plan', metavar='PLAN_FILE_CSV', required=True,
96 help="An execution plan (CSV file) with details of what footprint applications "
114 help="How to compose Twister test instance names using plan.txt columns. "
128 plan = []
132 plan = { f"{p['name']}/{p['feature']}/{p['board']}" : p for p in plan_vals }
133 return plan
136 def get_id_from_path(plan, in_path, max_levels=HWMv2_LEVELS): argument
148 # incorrect plan id
150 if f"{data_id['app']}/{data_id['feature']}/{data_id['board']}" in plan:
[all …]
|
| D | track.py | 15 description="Generate footprint data based on a predefined plan.",
17 parser.add_argument("-p", "--plan", help="Path of test plan", required=True)
27 with open(args.plan) as csvfile:
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 25 A request or plan to port an existing feature or enhancement to a particular
69 plan is a tactical document designed to capture and track the features planned
72 - The project roadmap communicates the why; a release plan details the what
73 - A release plan spans only a few months; a product roadmap might cover a year
84 can help the project present its plan in a compelling way to existing and new
87 they are still executing according to plan.
96 The release plan comes into play when the project roadmap's high-level strategy
97 is translated into an actionable plan built on specific features, enhancements,
100 The release plan communicates those features and enhancements slated for your
102 project plan, breaking the big ideas down into smaller projects the community
|
| D | tsc.rst | 68 Collaborate with the release manager and other stakeholders to plan and
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | conftest.py | 61 plan = TestPlan(env)
62 plan.parse_configuration(config_file=env.test_config)
63 return plan
79 plan = TestPlan(class_testplan.env)
80 plan.parse_configuration(config_file=class_testplan.env.test_config)
81 plan.add_configurations()
82 return plan.platforms
|
| D | test_testplan.py | 62 plan = TestPlan(class_env)
63 plan.parse_configuration(config_file=class_env.test_config)
65 plan.add_configurations()
66 print(sorted(plan.default_platforms))
67 …assert sorted(plan.default_platforms) == sorted(['demo_board_1/unit_testing', 'demo_board_3/unit_t…
69 plan.add_configurations()
70 assert sorted(plan.default_platforms) != sorted(['demo_board_1'])
75 plan = class_testplan
76 plan.testsuites = all_testsuites_dict
92 assert sorted(plan.get_all_tests()) == sorted(expected_tests)
[all …]
|
| /Zephyr-latest/scripts/tests/twister_blackbox/test_data/ |
| D | test_config.yaml | 7 A plan to be used verifying basic features
|
| /Zephyr-latest/scripts/tests/twister/test_data/ |
| D | test_config.yaml | 7 A plan to be used verifying basic zephyr features on hardware.
|
| /Zephyr-latest/tests/ |
| D | test_config.yaml | 7 A plan to be used verifying basic zephyr features on hardware.
|
| /Zephyr-latest/.github/workflows/ |
| D | footprint-tracking.yml | 91 ./scripts/footprint/track.py -p scripts/footprint/plan.txt
105 --plan ./scripts/footprint/plan.txt \
|
| D | twister-prep.yaml | 82 - name: Generate Test Plan with Twister
83 id: test-plan
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/ |
| D | README.rst | 8 If you plan to use this plugin with Twister, then you don't need to install it
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | reports.py | 44 def __init__(self, plan, env) -> None: argument
45 self.plan = plan #FIXME
46 self.instances = plan.instances
47 self.platforms = plan.platforms
48 self.selected_platforms = plan.selected_platforms
52 self.instance_fail_count = plan.instance_fail_count
672 f'{Fore.YELLOW}{self.plan.warnings + results.warnings}{Fore.RESET}'
673 if (self.plan.warnings + results.warnings)
|
| D | environment.py | 93 title="Test plan reporting",
94 description="Report the composed test plan details and exit (dry-run)."
158 help="""Output the test plan in a tree form.""")
826 run them. Useful if you're just interested in the test plan
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | index.rst | 19 should be set whether we plan to support and use the cache control in Zephyr
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 275 #. PRs related to items in the `Zephyr Release Plan`_ or those targeting
320 .. _Zephyr Release Plan: https://github.com/orgs/zephyrproject-rtos/projects/13
|
| D | external.rst | 117 migration plan.
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 1500 A plan to be used verifying basic zephyr features.
1503 A plan to be used verifying unit test.
1506 A plan to be used verifying integration.
1509 A plan to be used verifying acceptance.
1512 A plan to be used verifying system.
1515 A plan to be used verifying regression.
|
| /Zephyr-latest/scripts/ |
| D | twister | 174 running with -v or examining the test plan report (testplan.json)
|
| /Zephyr-latest/scripts/ci/ |
| D | test_plan.py | 410 help="JSON file with the test plan to be passed to twister")
511 # write plan
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.ipv6 | 108 of memory so you need to plan this and increase the network buffer
|
| /Zephyr-latest/drivers/serial/ |
| D | uart_hostlink.c | 377 /* We plan to use hostlink for logging, so no much sense in poll_in implementation */ in uart_hostlink_poll_in()
|
| /Zephyr-latest/scripts/build/ |
| D | llext_prepare_exptab.py | 223 # Plan of action:
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 154 If you plan to run Zephyr with one CPU only, you can skip it.
|
| /Zephyr-latest/drivers/watchdog/ |
| D | wdt_npcx.c | 362 * Plan clock frequency of T0 timer and watchdog timer as below: in wdt_npcx_init()
|
12
