Metersphere tutorial: how to assert when the returned result of the interface is null

background ：

Recently in use Metersphere When doing interface tests , When asserting , Some abnormal scenarios are to check whether the data cannot be found , The problems encountered in asserting are shared with you ：

First, let's look at if python in , What if the return result is empty ：

Next , Debug the interface in the platform , When making assertions ：

1、 Try assertions first Response Data Is it null perhaps "", Then the results are as follows ：

As can be seen from the screenshot above , The assertion ended in failure , It is possible that when the returned result is null , I don't know what has been done, but there are still bug, Anyway, the assertion in this case is inconvenient

2、 Use script assertions

Ideas ： Call the global function first prev.getResponseDataAsString() Get the return result . Then judge whether the returned result is == "" .

It turns out that doing so can assert success ：

The feeling of using ：

Although the platform is for people who can't write code , It provides certain convenience , however , There is also a certain learning cost , Especially when some scripts report errors , Debugging and positioning problems are not very convenient .

ps： I was in v1.18.xxx To try the version of , It is not ruled out that the later official fixes this problem , Or it's the wrong way to use it , Or right Response Data Your understanding is wrong, huh ！

Refer to summary

That's what this article wants to share , If you have any questions , Welcome to the official account - Xiaobo tests the way of growth and leaves messages for communication .

Writing is not easy , I think it's good. Please click three times , Your support is my biggest driving force for continuous output .