export default describe('searchCaseList', async (variables) => { const response = await…
- User
export default describe('searchCaseList', async (variables) => { const response = await login("xf_zeng", "Zz1322451175z") console.log(async_hooks.executionAsyncId()) console.log(async_hooks.triggerAsyncId()) const { request, response: searchCaseListRes } = await test({ url: { protocol: "http", host: "api.testhub.package.fat29.qa.nt.ctripcorp.com", pathname: "/bff/graphql/searchCaseList", query: null, hash: null, }, method: "post", headers: { "content-type": "application/json" }, cookies: { }, body: { query: "\n query SearchCaseList(\n moduleIds: [Int!]\n pageSize: PositiveInt\n filters: CaseFilters\n ) {\n searchCaseList(\n libraryId: moduleIds\n pageIndex: pageSize\n text: filters\n ) {\n total\n pageIndex\n pageSize\n list {\n id\n sort\n isCore\n createtime\n datachange_lasttime\n title\n type\n priority\n precondition\n platformType\n apiAutoCaseId\n requirementId\n requirementType\n libraryId\n tags {\n id\n name\n }\n module {\n id\n libraryId\n name\n parentId\n childIds\n children {\n id\n name\n }\n }\n steps {\n id\n floorId\n parentId\n expectation\n description\n }\n ownerInfo {\n __typename\n ... on EmployeeInfoResponseType {\n eid\n empName\n avatar\n valid\n deptName\n }\n ... on InvalidEmployee {\n message\n }\n }\n }\n }\n }\n", queryName: "searchCaseList", variables: variables }, }); console.log(async_hooks.executionAsyncId())
const body = await getBody(searchCaseListRes) assert.ok("searchCaseL1st") console.log(async_hooks.executionAsyncId()) console.log(async_hooks.triggerAsyncId()) const { response: caseDetailRes } = await getCaseDetail(body.data.searchCaseList.list[0].id) assert.ok('caseDetailRes') console.log(async_hooks.executionAsyncId()) console.log(async_hooks.triggerAsyncId()) const caseInfo = await getBody(caseDetailRes)})
为什么输出的async_hooks.executionAsyncId()不一样
- Assistant
输出的async_hooks.executionAsyncId()不一样是因为每个异步操作都有独立的执行上下文(execution context),每个执行上下文都有唯一的ID。在上述代码中,由于使用了多个异步操作,因此每个异步操作都有自己的执行上下文和执行上下文ID。在异步操作中,当调用异步函数时会创建一个新的执行上下文并在其中执行该函数,当该函数执行完成后,执行上下文会被销毁。因此,每个异步操作都有自己的执行上下文和执行上下文ID。