testVba failure on Windows

[Hossein Nourikhah]

Hello,

There are some tests that fail with different DPIs. I have encountered 
this failure before, using 3x scaling on Windows. Is it possible that he 
can run the test without scaling?

Regards,
Hossein

On 13.09.2023 09:09, Ilmari Lauhakangas wrote:
> I'm including test failure output from a new Windows developer. It's an 
> old test, added before 2011 at least. For some reason the test is 
> picking up the "Test Results" string appearing in the dialog. Opening 
> sc/qa/extras/testdocuments/window2.xls and clicking the button to run 
> tests works fine.
> 
> Ilmari
> 
> CPPUNIT_TEST_NAME="testVba" make CppunitTest_sc_vba_macro_test
> C:/cygwin/home/user/lode/opt/bin/make -j 12 -rs -f 
> C:/cygwin/home/user/lode/dev/core/Makefile.gbuild 
> CppunitTest_sc_vba_macro_test
> [build CUT] sc_vba_macro_test
> [_RUN_____] testVba::TestBody
> C:/cygwin/home/user/lode/dev/core/sc/qa/extras/vba-macro-test.cxx:458:testVba::TestBody
> equality assertion failed
> - Expected: OK
> - Actual  : Test Results
> ============
> 
>  Failed:  : Test SplitColumn: 0 (Test only applies to maximized Window 
> and at least has 800*600 solotion)
> Tests passed: 18
> Tests failed: 1
> 
> - script reported failure in file window2.xls
> 
> testVba::TestBody finished in: 18274ms
> C:/cygwin/home/user/lode/dev/core/sc/qa/extras/vba-macro-test.cxx(458) 
> : error : Assertion
> Test name: testVba::TestBody
> equality assertion failed
> - Expected: OK
> - Actual  : Test Results
> ============
> 
>  Failed:  : Test SplitColumn: 0 (Test only applies to maximized Window 
> and at least has 800*600 solotion)
> Tests passed: 18
> Tests failed: 1
> 
> - script reported failure in file window2.xls
> 
> Failures !!!
> Run: 1   Failure total: 1   Failures: 1   Errors: 0
> 
> Error: a unit test failed, please do one of:
> make CppunitTest_sc_vba_macro_test CPPUNITTRACE=TRUE # which is a 
> shortcut for the following line
> make CppunitTest_sc_vba_macro_test CPPUNITTRACE="'C:/Program 
> Files/Microsoft Visual Studio/2022/Community/Common7/IDE/devenv.exe' 
> /debugexe" # for interactive debugging in Visual Studio
> make CppunitTest_sc_vba_macro_test CPPUNITTRACE="drmemory 
> -free_max_frames 20" # for memory checking (install Dr.Memory first, 
> and put it to your PATH)
> 
> You can limit the execution to just one particular test by:
> 
> make CppunitTest_sc_vba_macro_test CPPUNIT_TEST_NAME="testXYZ" ...above 
> mentioned params...
> 
> make[1]: *** 
> [C:/cygwin/home/user/lode/dev/core/solenv/gbuild/CppunitTest.mk:130: 
> C:/cygwin/home/user/lode/dev/core/workdir/CppunitTest/sc_vba_macro_test.test] 
> Error 1
> make: *** [Makefile:169: CppunitTest_sc_vba_macro_test] Error 2

-- 
Hossein Nourikhah, Ph.D., Developer Community Architect
Tel: +49 30 5557992-65 | Email: hossein at libreoffice.org
The Document Foundation, Winterfeldtstraße 52, 10781 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint