Chinese character for assertion support
I would like to do an assertion test to see if the response contain certain chinese character. However, when I try to add the assertion content, all Chinese characters become "square" as seen in the ...
Forum Discussion
As you know, you tried and also another associated thread, currently none to address it seems.
But looking at your topic summary, it is causing confusion as it says "Chinese character for assertion" which is happening. Do you consider closing this topic as resolved? Display can be a different topic altogether, IMO.
But looking at your topic summary, it is causing confusion as it says "Chinese character for assertion" which is happening. Do you consider closing this topic as resolved? Display can be a different topic altogether, IMO.
As the Chinese character only fails to display at the assertion box as in the attached file. We are able to view it in the response XML tab. I suppose it is related to the display in the box?
- Yes, as you could also be able to assert it successfully.
Then this is the issue I am referring to. It does not make sense when you cannot view what you are asserting. If there is no proper chinese support, we may consider another automation product. I really hope soupUI have this support as I see it is a great tool.
- Well, the expected is known string (though it is not displayed, either you might have it from different location where it is being shown correct. And assertion is passed meaning that it is same string. This is what I believe.
More over, when it comes to automation, it is not really matter as long as machine can validate it correctly. Human do not have to go and see each and every input and output while the tests are passed. Of course, it is needed when in doubt.
There is aslo other possible way to see assertions goes fine:
Try asserting for negative using wrong string. And a postitive assert.
If still in doubt, Save the response into a file and open it in any editor of your choice to see it is the right.
Just curious: Have you bothered what request has gone in the request, first place? Response is later part.
That is why I was saying.
Of course we have gone through both negative and positive assertion. We also understand it is only a matter of failing to display, but when it comes to managing thousands of test cases, when a test case fail, we do not want to go through one by one and just to find out because we have asserted a wrong text.