From: "Max R. Carrara" <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-common v1 12/23] tests: sectionconfig: add isolated mode test structure
Date: Fri, 19 Dec 2025 20:44:47 +0100 [thread overview]
Message-ID: <20251219194511.840583-13-m.carrara@proxmox.com> (raw)
In-Reply-To: <20251219194511.840583-1-m.carrara@proxmox.com>
Similar to `schema_comparison_test.pl`, add `schema_isolated_test.pl`
for tests specific to PVE::SectionConfig's property isolation mode.
The purpose of these tests is to document the existing quirks of the
isolated mode of PVE::SectionConfig as well as to ensure that we catch
any regressions, should we need to make any changes to the inner
machinery of PVE::SectionConfig in the future.
This test script works similar to `schema_comparison_test.pl`, expect
that its cases are (obviously) not tested against their counterparts
in unified mode, as that simply doesn't apply for them.
Add a simple basic test case for child plugins that define identical
properties under isolated mode.
Signed-off-by: Max R. Carrara <m.carrara@proxmox.com>
---
test/SectionConfig/Makefile | 1 +
test/SectionConfig/schema_isolated_test.pl | 239 +++++++++++++++++++++
2 files changed, 240 insertions(+)
create mode 100755 test/SectionConfig/schema_isolated_test.pl
diff --git a/test/SectionConfig/Makefile b/test/SectionConfig/Makefile
index d1c2b1a..b0dfc93 100644
--- a/test/SectionConfig/Makefile
+++ b/test/SectionConfig/Makefile
@@ -1,5 +1,6 @@
TESTS = \
schema_comparison_test.pl \
+ schema_isolated_test.pl \
all:
diff --git a/test/SectionConfig/schema_isolated_test.pl b/test/SectionConfig/schema_isolated_test.pl
new file mode 100755
index 0000000..bc2c551
--- /dev/null
+++ b/test/SectionConfig/schema_isolated_test.pl
@@ -0,0 +1,239 @@
+#!/usr/bin/perl
+
+use v5.36;
+
+use lib qw(
+ ..
+ ../../src/
+);
+
+use Data::Dumper;
+
+$Data::Dumper::Terse = 1;
+$Data::Dumper::Indent = 1;
+$Data::Dumper::Useqq = 1;
+$Data::Dumper::Deparse = 1;
+$Data::Dumper::Quotekeys = 0;
+$Data::Dumper::Sortkeys = 1;
+$Data::Dumper::Trailingcomma = 1;
+
+use Test::More;
+
+use SectionConfig::Helpers qw(
+ symbol_table_has
+ get_subpackages
+ get_plugin_system_within_package
+ dump_symbol_table
+);
+
+package TestPackage {
+ use Carp qw(confess);
+
+ sub expected_isolated_createSchema($class) {
+ confess "not implemented";
+ }
+
+ sub expected_isolated_updateSchema($class) {
+ confess "not implemented";
+ }
+
+ sub desc($class) {
+ return undef;
+ }
+};
+
+package IdenticalPropertiesOnDifferentPlugins {
+ use base qw(TestPackage);
+
+ sub desc($class) {
+ return "defining identical properties on different plugins does not lead to"
+ . " 'oneOf' being used inside either createSchema or updateSchema";
+ }
+
+ package IdenticalPropertiesOnDifferentPlugins::PluginBase {
+ use base qw(PVE::SectionConfig);
+
+ my $DEFAULT_DATA = {};
+
+ sub private($class) {
+ return $DEFAULT_DATA;
+ }
+ };
+
+ package IdenticalPropertiesOnDifferentPlugins::PluginOne {
+ use base qw(IdenticalPropertiesOnDifferentPlugins::PluginBase);
+
+ sub type($class) {
+ return 'one';
+ }
+
+ sub properties($class) {
+ return {
+ 'prop-one' => {
+ type => 'string',
+ optional => 1,
+ },
+ 'prop-two' => {
+ type => 'string',
+ optional => 1,
+ },
+ };
+ }
+
+ sub options($class) {
+ return {
+ 'prop-one' => {
+ optional => 1,
+ },
+ 'prop-two' => {
+ optional => 1,
+ },
+ };
+ }
+ };
+
+ package IdenticalPropertiesOnDifferentPlugins::PluginTwo {
+ use base qw(IdenticalPropertiesOnDifferentPlugins::PluginBase);
+
+ sub type($class) {
+ return 'two';
+ }
+
+ sub properties($class) {
+ return {
+ 'prop-one' => {
+ type => 'string',
+ optional => 1,
+ },
+ 'prop-two' => {
+ type => 'string',
+ optional => 1,
+ },
+ };
+ }
+
+ sub options($class) {
+ return {
+ 'prop-one' => {
+ optional => 1,
+ },
+ 'prop-two' => {
+ optional => 1,
+ },
+ };
+ }
+ };
+
+ sub expected_isolated_createSchema($class) {
+ return {
+ type => 'object',
+ additionalProperties => 0,
+ properties => {
+ type => {
+ type => 'string',
+ enum => [
+ "one", "two",
+ ],
+ },
+ 'prop-one' => {
+ type => 'string',
+ optional => 1,
+ },
+ 'prop-two' => {
+ type => 'string',
+ optional => 1,
+ },
+ },
+ };
+ }
+
+ sub expected_isolated_updateSchema($class) {
+ return {
+ type => 'object',
+ additionalProperties => 0,
+ properties => {
+ type => {
+ type => 'string',
+ enum => [
+ "one", "two",
+ ],
+ },
+ 'prop-one' => {
+ type => 'string',
+ optional => 1,
+ },
+ 'prop-two' => {
+ type => 'string',
+ optional => 1,
+ },
+ $SectionConfig::Helpers::UPDATE_SCHEMA_DEFAULT_PROPERTIES->%*,
+ },
+ };
+ }
+}
+
+sub test_compare_deeply($got, $expected, $test_name, $test_package) {
+ $test_name = "$test_package - $test_name";
+ my $description = $test_package->desc();
+
+ if (!is_deeply($got, $expected, $test_name)) {
+ note("\nDescription: ", $description // "(none)", "\n");
+ note("Got:");
+ note(Dumper($got));
+ note("Expected:");
+ note(Dumper($expected));
+ note("=" x 40);
+ }
+
+ return;
+}
+
+sub init_and_run_tests($package) {
+ my $system = get_plugin_system_within_package($package);
+
+ my ($base, $plugins) = $system->@{qw(base plugins)};
+
+ for my $plugin ($plugins->@*) {
+ $plugin->register();
+ }
+
+ $base->init(property_isolation => 1);
+
+ test_compare_deeply(
+ $base->createSchema(),
+ $package->expected_isolated_createSchema(),
+ "isolated - createSchema comparison",
+ $package,
+ );
+
+ test_compare_deeply(
+ $base->updateSchema(),
+ $package->expected_isolated_updateSchema(),
+ "isolated - updateSchema comparison",
+ $package,
+ );
+
+ return;
+}
+
+sub main() {
+ my $subpackages = get_subpackages('main');
+
+ my $test_packages = [];
+
+ for my $package (sort $subpackages->@*) {
+ if ($package !~ m/TestPackage/ && $package->isa('TestPackage')) {
+ push($test_packages->@*, $package);
+ }
+ }
+
+ for my $package ($test_packages->@*) {
+ init_and_run_tests($package);
+ }
+
+ done_testing();
+
+ return 0;
+}
+
+main();
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-12-19 19:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 19:44 [pve-devel] [PATCH pve-common v1 00/23] Document PVE::SectionConfig Peculiarities Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 01/23] sectionconfig: remove unused variable in get_property_schema() Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 02/23] tests: sectionconfig: add comparison test structure Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 03/23] tests: sectionconfig: add test case for fixed props in updateSchema Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 04/23] tests: sectionconfig: add case for unused properties Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 05/23] tests: sectionconfig: add case for unused optional default properties Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 06/23] tests: sectionconfig: add case for opt. default prop being req. once Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 07/23] tests: sectionconfig: add case for opt. default prop requirde by all Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 08/23] tests: sectionconfig: add case for unused required default properties Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 09/23] tests: sectionconfig: add case for req. default prop being req. once Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 10/23] tests: sectionconfig: add case for required default prop req. by all Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 11/23] tests: sectionconfig: add case for required default props opt. for all Max R. Carrara
2025-12-19 19:44 ` Max R. Carrara [this message]
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 13/23] tests: sectionconfig: add case for an ident. prop on two plugins Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 14/23] tests: sectionconfig: add case for same prop. w/ different optionality Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 15/23] tests: sectionconfig: add case for differing opt. default prop uses Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 16/23] tests: sectionconfig: add case for differing req. " Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 17/23] sectionconfig: correct docs regarding global props in unified mode Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 18/23] sectionconfig: reword docs regarding property usage in isolated mode Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 19/23] sectionconfig: extend / correct docstring of `private()` method Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 20/23] sectionconfig: note that a prop must be defined through a JSONSchema Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 21/23] sectionconfig: note that props added by plugins are always optional Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 22/23] sectionconfig: note that `createSchema()` is universal for all plugins Max R. Carrara
2025-12-19 19:44 ` [pve-devel] [PATCH pve-common v1 23/23] sectionconfig: correct example in docstring of `updateSchema()` Max R. Carrara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251219194511.840583-13-m.carrara@proxmox.com \
--to=m.carrara@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.