Applicability again

Question

question

dclaar Suspended asked Oct 8, '09 dclaar Suspended posted Oct 8, '09

Applicability again

I'm trying to create a RM for md5sum, which I invoke as /usr/bin/md5sum. What is the appropriate applicabilty?

With wildcard?
md5sum

*md5sum

With Case insensitive?

I guess, the broader question is, how is the comparison done? Does it need to match from the beginning? Does wildcard include paths? What are the rules?

I'm asking because I can't seem to get the command to recognize the RM. It is in common_linux, and I've tried:

md5sum

*md5sum

/usr/bin/md5sum

And none of them work!

   <result>
      <action actionType="command">
         <command>
            <body>/usr/bin/md5sum $target</body>
         </command>
      </action>
      <response isAutoMapped="true">

<mappingInfo>
   <projects>
      <project>LinuxTrafficGenerator</project>
      <project>common_linux</project>
   </projects>
   <candidateMaps/>

iTest response map

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2009-10-08T16:35:07Z

YujieL answered Oct 8, '09 YujieL posted Oct 8, '09

It is case insensitive. I have a hunch that you do need to put a * at the beginning, but I need to double check.

13

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

dclaar commented · Oct 08, 2009 at 04:55 PM

Something must be messed up. I can't get this command to find the response map no matter what I put in applicability. Any thoughts on what I can check?

Applicability has the check box checked, non session types checked, Action: command Target: blank, Command: Tried lots of things, Compare properties using: Wildcard, Map priority 50.

Command has Action: command, Session ${source}_cli, although I also tried tg_cli. Description has /usr/bin/md5sum $file

Post processing has "Use the response map library configured for the session", and the output indicates that it is looking in the correct library.

0 ·

YujieL dclaar commented · Oct 08, 2009 at 05:04 PM

If the applicability has the word ${source}_cli in it, that won't work because ${} is going to be replaced by the variable value in the test case, and we take the applicability data as is, no substitution involved.

0 ·

dclaar YujieL commented · Oct 08, 2009 at 05:31 PM

No, applicability doesn't have ${} in it.

common_linux has builder: iTest Documents Builder.

Interesting, when you look at properties, it creates a META-INF/MANIFEST.MF file, which svn thinks needs to be committed. Why is that?

0 ·

dclaar dclaar commented · Oct 08, 2009 at 05:58 PM

*md5sum* works.

0 ·

YujieL dclaar commented · Oct 08, 2009 at 06:55 PM

What properties are you referring to? META_INF folder and manifest.mf are created if you create a new plugin project in Eclipse. If the project is just an iTest project, then you shouldn't see the META_INF folder or manifest.mf file. Are you using iTest in plugin mode or RCP mode? If you're using iTest in plugin mode, is it possible that you created a plugin project?

0 ·

dclaar YujieL commented · Oct 08, 2009 at 07:12 PM

Nope. It is kind of weird. All of a sudden several (but not all) of my projects had META_INF. And automatic build was turned off. It is almost like eclipse hiccuped somehow, and got confused. I reverted all of 'em, and they went away.

I'm not sure what RCP mode is; I'm using the iTest GUI, and I have not tried to do any plugin stuff (yet!)

These are projects that have been in this workspace for months: I haven't created any new ones or anything like that.

It's just weird.

Doug

0 ·

PaulD dclaar commented · Oct 08, 2009 at 08:10 PM

iTest does, in fact, create META_INF files for ITARs. But I thought these would only be created inside the ITAR file itself, and not inside the workspace. Have you generated ITARs from these? If so, maybe we have a bug where we're leaving those things around?

0 ·

dclaar PaulD commented · Oct 08, 2009 at 11:19 PM

I haven't created any itars.

0 ·

GuanghongY PaulD commented · Oct 12, 2009 at 05:08 PM

Let me clarify. iTest now does create META-INF and the included MANIFEST.MF file. This file is to keep track of dependent projects (for creating iTars) and chained response map projects (for response map chaining). Both of these can be configured in Project Properties pages. This manifest file is created/updated whenever the builder is triggered. The builder can be triggered when user changes things in Project Properties (on iTest Project Dependencies, Project Refernces, or Response Map Chaining), or rebuilds the project, or changes some files in a project and has the automatical building turned on. Please check if any of these scenarios you might have gone into that the builder was triggered to create the manifest file.

0 ·

PaulD GuanghongY commented · Oct 12, 2009 at 08:18 PM

You are absolutely right! I had forgotten about inter-project dependencies.

These files are now important because they provide the explicit information about what other project(s) any given project depends on. This information is important because it means that we can now be definitive about knowing what project dependencies exist when, for example, building ITARs.

So these should, in fact, be checked into version control.

0 ·

YujieL commented · Oct 08, 2009 at 04:59 PM

First thing to check is that automatic build is turned on. Otherwise, the response map catalog won't be built. In the response map library project, there should be a .maplib file, which is the catalong containing response map URIs and the applicability data. Make sure the response map you want to use is in the catalog.

0 ·

YujieL YujieL commented · Oct 08, 2009 at 05:01 PM

I just verified that you do indeed need a * at the beginning

0 ·

dclaar YujieL commented · Oct 08, 2009 at 05:02 PM

Shoot, somehow I got a META-INF/MANIFEST.MF file. Blew it away. Also, automatic build was turned off. Don't know how that happened, it had been on before!

Manifest-Version: 1.0
iTest-Manifest-Version: 1.0
iTest-Dependent-Project:

0 ·

question