Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-97652

Improve test to show crashes and Jni env in Android

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • Icon: P2: Important P2: Important
    • 6.4.0 Beta1
    • 6.2
    • Testing: qtestlib
    • None
    • Android
    • 3d9e56aa6c (qt/qtbase/dev) 3d9e56aa6c (qt/tqtc-qtbase/dev)
    • 2021wk44POAndroid&Mobile, 2021wk46POAndroid&Mobile, 2021wk48POAndroid&Mobile, 2021wk50POAndroid&Mobile, 2022wk02FOAndroid&Automotive, 2022wk04FOAndroid&Automotive, 2022wk06FOAndroid&Automotive

      When a signal like Segmentation Fault or JNI exception happens while testing with ctest, the execution of the android app is stopped and the output.txt is also stopped.

      In Android we can see the stacktrace using logcat, but the ctest output just shows that the test passed (if no test case failed unit then).

      It is possible to see if the test is stopped midway if it does not run the cleanup phase. But when running multiple tests, this is doesn't warn that something went wrong, or what happened for the test to stop.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            samuelmira Samuel Mira
            samuelmira Samuel Mira
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: