Re: [Pydev-code] Some problems running Unit Tests

[Fabio Z. <fa...@gm...>]

Hi Mark,

On Thu, Jan 21, 2016 at 4:17 PM, Mark Leone <mid...@ve...>
wrote:

> I'm running the PyDev unit tests to get a baseline before starting some
> work on mods to be submitted as a pull request. I believe I have
> everything defined correctly in
>
> org.python.pydev.core/tests/org/python/pydev/core/TestDependent.linux.properties,
> with the exception of the IronPython properties. I'm running on CentOS
> 6.7, and don't care to install IronPython, which AFAICT requires the
> installation and configuration of the Mono framework to get it working
> on Linux.
>
> I'm getting some failures, most of which seem to be expected, but two
> are not. Here's what I'm doing and the results.
>
> 1. Right-click on com.python.pydev.runalltests and select Run As -->
> Junit Test
>
> Failures which I think are expected:
>
> - IronPython tests fail, since I don't have IronPython installed
> ​​
>
> - There is a failure in org.python.pydev.debug.pyunit.PyUnitViewTest,
> which a comment in the code says is to be expected.
> - All the tests in com.python.pydev.runalltests2.AllWorkbenchTests fail,
> which I assume is expected since I launched the tests as JUnit tests,
> not JUnit Plug-In tests.
>

​You can actually just right click "AllTests" ​> Run As > JUnit test and
"AllWorksbenchTests" > Run As > JUnit Plugin Test (you could also run all
as junit plugin tests, but as it takes more time to setup, usually I run
one and then the other).


>
> A failure I don't expect:
>
> In PythonShellTest at line 95, and IndexOutOfBounds exception is thrown.
> The "list" object is empty, apparently because the import for the "math"
> module fails. I believe I have all the python locations and files
> specified properly, and if I launch a python shell manually, I can
> successfully import the math module.
>

​Well, I don't have that failure here, so, it really seems unexpected,
although it's hard to know why without further details -- it probably means
you have some issue communicating with the shell (so, maybe you could try
debugging it there?)


>
> 2. Right-click on com.python.pydev.runalltests and select Run As -->
> Junit Plug-In Test.
>
> A failures which I think is expected:
>
> - There is an initialization error in
> com.python.pydev.runalltests2.AllTests, saying "There are no test cases
> to run". I assume this is expected, since I'm running JUnit Plug-In Tests.
>

​Yes, this is expected.​


>
> A failure I don't expect:
>
> - A ClassCastException is thrown on line 106 of
> ​​
> AppEngineConfigWizardPageTestWorkbench
>
> AppEngineConfigWizardPage appEnginePage = (AppEngineConfigWizardPage)
> pages[1];
>
> The message is
> "org.python.pydev.ui.wizards.project.NewProjectExistingSourcesWizardPage
> cannot be cast to
>
> org.python.pydev.customizations.app_engine.wizards.AppEngineConfigWizardPage"
>

This is expected (it's an error I've been lazy to fix).


>
> Is this the way I should be running the tests? Are the failures that I
> say are expected in fact not a problem? Are the two unexpected failures
> indeed a problem, and if so, any ideas what's causing them or how to
> resolve them?
>

​Yes, this is the expected way you should be running the tests (although
you can just narrow things down as I mentioned earlier) -- as for being a
problem, each case is a case -- if you could debug why the first one is
failing on your system, that'd be nice... as for the other, I'll take a
look at it.

Best Regards,

Fabio


>
> -Mark
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>