Changes between Version 1 and Version 2 of Obsolete/Development/Code/TestingComponents

Timestamp:

Apr 23, 2012, 9:31:44 PM (14 years ago)

Author:

munoz

Comment:

--

Obsolete/Development/Code/TestingComponents

@@ -119 +119 @@
 === Testing the `Configure` method ===
 
-This method should have almost no logic. But it still deserves some testing. It must receive a valid `EDG::CCM::Configuration` object from a profile. And handling this is done by `Test::Quattor`.
+This method should have almost no logic. But it still deserves some testing. It must receive a valid `EDG::CCM::Configuration` object from a profile. And handling this is done by `Test::Quattor`. This is how we do it:
+
+1. We have a set of test profiles. They are minimalistic, and have no dependencies on any "standard" templates. Just assign a few values to fill in your component structure. For instance:
+{{{
+#!sh
+object template test_profile;
+
+prefix "/software/components/foo";
+"a" = 1;
+"b" = 2;
+}}}
+1. This profile must be compiled, and a cache must be created for it. The `Test::Quattor` comes in hand here: If you pass any arguments to it, it will compile them and prepare the correct cache:
+{{{
+#!perl
+use Test::Quattor qw(test_profile another_test_profile);
+}}}
+1. And then, you'll want it to serve you the configuration for some of these, right?
+{{{
+#!perl
+my $config = get_config_for_profile("test_profile");
+}}}
+1. And now, you can just run `Configure` on it:
+{{{
+#!perl
+$comp->Configure($config);
+}}}
+
+And test whatever you need to test. Simple, right?