MDS/openide
1
0
Fork 0
mirror of https://gitflic.ru/project/openide/openide.git synced 2026-09-27 10:03:11 +07:00
Code Issues Packages Projects Releases Wiki Activity

Use the appropriate TypeEvalContext in tests (PY-15558)

Browse Source
This commit is contained in:
Andrey Vlasovskikh
2015-11-16 19:22:23 +03:00
parent b925c07ab6
commit c2ad6bce61
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
python/testSrc/com/jetbrains/python/PyResolveCalleeTest.java
+3 -1
View File
@@ -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() {