WSTF `StepName` max length

Answered

Tunç Atalan

February 22, 2023 16:33

Experiencing trying to import reports in WSTF to the server, some step names (see below) in our report are exceeding the max length that is allowed for `StepName` as WATS Standard Format Description also suggests it is limited to 100 characters. However, we already have a lot of reports that come with long step names and I am curious if there is any way to extend the max length for fields/columns?

EOL-CLS-13 Outputs (RF) / Sweep Outputs / Output Channel 1 / Sweep Frequency / Attenuation Sweep Sequence / Sweep Attenuation / Attenuation = 2 dB / Check Output Power

I would appreciate if you can help me out on that!

Comments

6 comments

Anders Kristiansen

February 23, 2023 08:06
There is no way to increase the max length for step name.

You can set the validationMode parameter to AutoTruncate, then the report will not throw error when a step name is too long, instead removing everything after 100 characters.

You can group steps into sequences:

Example (-> means tab):
```
SequenceCall->SubSeq1->->->->->->->->10->seq call info->->->
NumericLimitTest->Test1.1->->2->1->5->GELE->V->Passed->2->Test info->->->
NumericLimitTest->Test1.2->->3->1->5->GELE->V->Passed->8->Test info->->->
EndSequenceCall->->->->->->->->P
```
See https://virinco.zendesk.com/hc/en-us/articles/207424623-Wats-Standard-Text-Format-WSTF- for more info.

In this case, maybe the steps could look like this?
```
SequenceCall->EOL-CLS-13 Outputs (RF) / Sweep Outputs / Output Channel 1->->->->->->->->->
SequenceCall->Sweep Frequency / Attenuation Sweep Sequence->->->->->->->->->
NumericLimitTest->Sweep Attenuation / Attenuation = 2 dB / Check Output Power->->->->->->->->->
...
EndSequenceCall->->->->->->->->->
EndSequenceCall->->->->->->->->->
```
Especially if you have more Sweep Attenuation steps.

Maybe you can log some of the information you have in step name as StepReportText instead, and make the step name shorter?
0

Comment actions Permalink

Tunç Atalan

February 24, 2023 10:21

Thanks for your response Anders. I did go with the implementation of sequences which turned out to be a good option at least in our raw reports. However, trying to import them to the server a new issue popped up where identical `StepName` entries, although they are wrapped up in different sequences, caused the error below:

Start parsing: 23/02/2023 17:58:28
Parse error in line 122: ReadFile Cannot add multiple single tests to single test step.
Line: NumericLimitTest    Check Input is True        1    1    0    EQ        PASS    0.0971    
Parse error in line 122: ImportReport: Cannot add multiple single tests to single test step.
Line: 122

The snippet of the report where the above-mentioned error occurs is:

SequenceCall    EOL-CLS-07 Markers                                    
SequenceCall     Marker Output States / Check Marker Outputs / Marker 1                                    
NumericLimitTest    Check Input is True        1    1    0    EQ        PASS    0.8888    
EndSequenceCall                                        
EndSequenceCall                                        
SequenceCall    EOL-CLS-07 Markers                                    
SequenceCall     Marker Output States / Check Marker Outputs / Marker 2                                    
NumericLimitTest    Check Input is True        1    1    0    EQ        PASS    0.2301    
EndSequenceCall                                        
EndSequenceCall

I would expect that the reason to have `SequenceCall` and `EndSequenceCall` is to isolate that particular test step, thus another test step from a different sequence should not be a problem in terms of having identical names. Could you perhaps provide any workarounds if possible? We will have this pattern recurring along the report...

Anders Kristiansen

February 24, 2023 11:51

You are correct, this should work. I found a bug in the WATS Client that causes this. I will get that fixed.

Also do you need the second 'EOL-CLS-07 Markers' sequence? You can add more sequences (and steps) before ending the first:

SequenceCall    EOL-CLS-07 Markers                                                        
SequenceCall    Marker Output States / Check Marker Outputs / Marker 1                                                        
NumericLimitTest    Check Input is True        1    1    0    EQ        PASS    0.8888                        
EndSequenceCall                                                            
SequenceCall    Marker Output States / Check Marker Outputs / Marker 2                                                        
NumericLimitTest    Check Input is True        1    1    0    EQ        PASS    0.2301                        
EndSequenceCall                                                            
EndSequenceCall

Tunç Atalan

February 27, 2023 10:59
Good to hear it will get fixed! Do you perhaps have any insight about when it would be fixed?

As for combining child steps under EOL-CLS-07 Markers; we record every test step as an individual line that always contains the parent name (e.g. EOL-CLS-07) so it wouldn't work out to combine the child steps as every test step is independent from each other.
0

Comment actions Permalink
Anders Kristiansen

February 27, 2023 13:12
I just released a new version with the fix today! Version 6.1.81.
1

Comment actions Permalink
Tunç Atalan

February 27, 2023 16:50
That's great. It indeed worked out for us to be able to import our reports. Thanks a lot for the rapid support and the fix!
0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?