Forum Discussion

merose's avatar
merose
New Contributor
4 years ago
Solved

How to turn off stylization of parameters in the Test Player – screws up cut-and-paste

Is there a way to turn off the blue box stylization of parameter values in the Test Player? It's screwing up our testers because when they cut-and-paste into a terminal window a command that includes variables, it often includes invisible garbage characters such as 0x81. This causes problems in some terminal commands or makes strange file names that are hard to fix.

 

Ideally, the variable values are just ordinary text in the Test Player, or a <span> with stylization that does not insert extra characters. (The stylization you've chosen has other problems, too, such as extra padding around the variable value that makes it look like you're supposed to type spaces around the value. You're trying to do too much, and it makes the Test Player less usable.)

  • Possibly solved: It looks like whenever you type a parameter name in a test step ("{" parameter name "}"), Zephyr Scale changes the parameter name into a <span>...</span>, but also adds a nonbreaking space: &nbsp;

     

    This is what is causing cut-and-paste problems. The nonbreaking space is a Unicode \u00A0 character, which on some platforms is cut-and-pasted as the UTF-8 bytes for that character, not as an ordinary space.

     

    Workaround: Whenever you add a parameter to a test step, immediately backspace to delete the nonbreaking space. You can also check your test cases by exporting to XML and searching for "&nbsp;". If non are found, the text of the test steps can be safely cut-and-pasted by the person executing the test.

     

    It would be convenient if Zephyr Scale did not add the nonbreaking space – or any space – when adding a parameter to a test step.

1 Reply

  • merose's avatar
    merose
    New Contributor

    Possibly solved: It looks like whenever you type a parameter name in a test step ("{" parameter name "}"), Zephyr Scale changes the parameter name into a <span>...</span>, but also adds a nonbreaking space: &nbsp;

     

    This is what is causing cut-and-paste problems. The nonbreaking space is a Unicode \u00A0 character, which on some platforms is cut-and-pasted as the UTF-8 bytes for that character, not as an ordinary space.

     

    Workaround: Whenever you add a parameter to a test step, immediately backspace to delete the nonbreaking space. You can also check your test cases by exporting to XML and searching for "&nbsp;". If non are found, the text of the test steps can be safely cut-and-pasted by the person executing the test.

     

    It would be convenient if Zephyr Scale did not add the nonbreaking space – or any space – when adding a parameter to a test step.