test: clean the temporary data in etcd at the end of test case

[membphis]

the current way:

apisix-dashboard/api/test/e2e/route_test.go

Lines 227 to 260 in 96e3ad1

	func TestRoute_Delete_Routes_With_Hosts(t *testing.T) {
	tests := []HttpTestCase{
	{
	caseDesc: "delete route",
	Object: ManagerApiExpect(t),
	Method: http.MethodDelete,
	Path: "/apisix/admin/routes/r1",
	Headers: map[string]string{"Authorization": token},
	ExpectStatus: http.StatusOK,
	},
	{
	caseDesc: "delete not exist route",
	Object: ManagerApiExpect(t),
	Method: http.MethodDelete,
	Path: "/apisix/admin/routes/not-exist",
	Headers: map[string]string{"Authorization": token},
	ExpectStatus: http.StatusNotFound,
	},
	{
	caseDesc: "hit the route just deleted",
	Object: APISIXExpect(t),
	Method: http.MethodGet,
	Path: "/hello1",
	Headers: map[string]string{"Host": "bar.com"},
	ExpectStatus: http.StatusNotFound,
	ExpectBody: "{\"error_msg\":\"404 Route Not Found\"}\n",
	Sleep: sleepTime,
	},
	}
	for _, tc := range tests {
	testCaseCheck(tc)
	}
	}

The current way is to completely depend on the developer and bring extra work to the test case maintainer.

we need a common way to clean all of the temporary data in etcd after running the test cases of each file.

[membphis]

I think this feature is useful. The E2E test cases are unstable, I think this feature will improve the stability of E2E testing.

[membphis]

@nic-chen @ShiningRush do you think we can implement this feature at milestone 2.2?

[ShiningRush]

It is useful and easy to implement with go's TestMain, We can ensure etcd is fresh before start test.

[membphis]

@gxthrj @nic-chen do you know TestMain ? Any suggestions?

[nic-chen]

I think we need to clear ETCD data without distinction before or after running test, by TestMain.

[gxthrj]

The TestMain way is a test suite like ginkgo, we can use it make struct more clear, but I still like ginkgo mode.

[juzhiyuan]

cc @starsz

[membphis]

any news? @starsz

[starsz]

any news? @starsz

Sorry for I am late. I think we can do this work when we use ginko framework.
As far as I know, we will use ginko framework in M2.4, so this will be solved at that time.