|
KiCad PCB EDA Suite
|
Test for issue #18119: Bus net connections not propagating correctly through hierarchy when bus member wire names differ from parent bus wire names. More...
#include <qa_utils/wx_utils/unit_test_utils.h>#include <schematic_utils/schematic_file_util.h>#include <connection_graph.h>#include <schematic.h>#include <sch_sheet.h>#include <sch_screen.h>#include <sch_symbol.h>#include <sch_pin.h>#include <settings/settings_manager.h>#include <locale_io.h>Go to the source code of this file.
Classes | |
| struct | ISSUE18119_FIXTURE |
Functions | |
| BOOST_FIXTURE_TEST_CASE (Issue18119BusHierarchy, ISSUE18119_FIXTURE) | |
| Test that bus member connections propagate correctly through hierarchy when wire names differ on each side of the hierarchy. | |
Test for issue #18119: Bus net connections not propagating correctly through hierarchy when bus member wire names differ from parent bus wire names.
The schematic has:
Expected: BUS0 should be connected to VCC (through OUT_0), BUS1 should be connected to GND (through OUT_1).
The bug: BUS1 does not connect to GND because the net name propagation through the bus hierarchy doesn't work correctly when wire names (BUS0/BUS1) differ from bus member names (SUB_BUS0/SUB_BUS1).
Definition in file test_issue18119_bus_hierarchy.cpp.
| BOOST_FIXTURE_TEST_CASE | ( | Issue18119BusHierarchy | , |
| ISSUE18119_FIXTURE | ) |
Test that bus member connections propagate correctly through hierarchy when wire names differ on each side of the hierarchy.
Expected connectivity:
Note: R1 is between OUT_0 and VCC, creating two separate nets:
Definition at line 80 of file test_issue18119_bus_hierarchy.cpp.
References dummy, CONNECTION_GRAPH::GetNetMap(), SCH_SYMBOL::GetRef(), KI_TEST::LoadSchematic(), pin, and SCH_PIN_T.