From c2ad6bce612d14d391efd2b7ba32d15e48872391 Mon Sep 17 00:00:00 2001 From: Andrey Vlasovskikh Date: Mon, 16 Nov 2015 19:22:23 +0300 Subject: [PATCH] Use the appropriate TypeEvalContext in tests (PY-15558) --- python/testSrc/com/jetbrains/python/PyResolveCalleeTest.java | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/python/testSrc/com/jetbrains/python/PyResolveCalleeTest.java b/python/testSrc/com/jetbrains/python/PyResolveCalleeTest.java index 486396a01a53..b7dbfd6d3ab8 100644 --- a/python/testSrc/com/jetbrains/python/PyResolveCalleeTest.java +++ b/python/testSrc/com/jetbrains/python/PyResolveCalleeTest.java @@ -21,6 +21,7 @@ import com.jetbrains.python.fixtures.PyTestCase; import com.jetbrains.python.psi.PyCallExpression; import com.jetbrains.python.psi.PyFunction; import com.jetbrains.python.psi.resolve.PyResolveContext; +import com.jetbrains.python.psi.types.TypeEvalContext; /** * Tests callee resolution in PyCallExpressionImpl. @@ -32,7 +33,8 @@ public class PyResolveCalleeTest extends PyTestCase { private PyCallExpression.PyMarkedCallee resolveCallee() { PsiReference ref = myFixture.getReferenceAtCaretPosition("/resolve/callee/" + getTestName(false) + ".py"); PyCallExpression call = PsiTreeUtil.getParentOfType(ref.getElement(), PyCallExpression.class); - return call.resolveCallee(PyResolveContext.defaultContext()); + final TypeEvalContext context = TypeEvalContext.codeAnalysis(myFixture.getProject(), myFixture.getFile()); + return call.resolveCallee(PyResolveContext.noImplicits().withTypeEvalContext(context)); } public void testInstanceCall() {