Mailinglist Archive: yast-devel (129 mails)

< Previous Next >
[yast-devel] Weirdness in YaST testsuites
  • From: Lukas Ocilka <lukas.ocilka@xxxxxxx>
  • Date: Thu, 01 Nov 2007 14:23:04 +0100
  • Message-id: <4729D338.6050506@xxxxxxx>
Hi,

All of you have definitely already written some testsuite for your YaST
module. That's right because writing testsuites (that are executed in
the RPM-build-time) can prevent from getting more bugreports later.

Anyway, sometimes there are some problems between chair and keyboard
that need a small hint from some other developer (Mvidner for today ;)).

Today's problem were constructors in imported modules. I was unable to
make testsuite pass even if everything seemed to be all right:

--- cut (shortened) ---
include "testsuite.ycp";
import "Bootloader";

map EXECUTE = $[ "target" : $[ "bash_output" : $[] ] ]
TESTSUITE_INIT ([READ, WRITE, EXECUTE], nil);

TEST (``(Bootloader::Read()), [READ, WRITE, EXECUTE], nil);
--- cut (shortened) ---

make check kept returning:
Encoding.ycp:33 Can't convert value '0' to type 'map'

Encoding.ycp:33 contains:
map m = (map) SCR::Execute( .target.bash_output, "locale -k charmap" );

So, has what helped?
Just moving the >import "Bootloader";< after >TESTSUITE_INIT< call.

--- cut (shortened) ---
include "testsuite.ycp";

map EXECUTE = $[ "target" : $[ "bash_output" : $[] ] ]
TESTSUITE_INIT ([READ, WRITE, EXECUTE], nil);

import "Bootloader";

TEST (``(Bootloader::Read()), [READ, WRITE, EXECUTE], nil);
--- cut (shortened) ---

That's all for now. Next time "How to make your computer implement
manager's FATE requests automagically -- Three steps to a better life".

Have a nice day
Lukas

--

Lukas Ocilka, YaST Developer (xn--luk-gla45d)
-----------------------------------------------------------------
SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

< Previous Next >
List Navigation
Follow Ups