Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. QT Quick Test Case XML test results malformed after QT6.7.2 upgrade : cleanupTestCase incomplete?
Forum Updated to NodeBB v4.3 + New Features

QT Quick Test Case XML test results malformed after QT6.7.2 upgrade : cleanupTestCase incomplete?

Scheduled Pinned Locked Moved Unsolved QML and Qt Quick
2 Posts 2 Posters 213 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jmcd
    wrote on last edited by
    #1

    Hello.

    We are currently upgrading from QT5.15 to QT6.7 and have noticed that due to some changes in TestCase.qml and new TestSchedule.qml , it appears XML testresults output are never correctly closed.

    E.g. after running simple app startup test:

    <TestCase name="UITest">
      <Environment>
        <QtVersion>6.7.2</QtVersion>
        <QtBuild>Qt 6.7.2</QtBuild>
        <QTestVersion>6.7.2</QTestVersion>
      </Environment>
      <TestFunction name="Null test::initTestCase">
        <Incident type="pass" file="" line="0" />
        <Duration msecs="28.9662"/>
      </TestFunction>
    <TestFunction name="Null test::test_WaitForStart">
        <Message type="qinfo" file="" line="0">
            <Description><![CDATA[qml: Waited for app to start]]></Description>
         </Message>
        <Incident type="pass" file="" line="0" />
        <Duration msecs="1265.11"/>
      </TestFunction>
     <TestFunction name="Null test::cleanupTestCase">
      <Duration msecs="4071.77"/>
    </TestCase>
    

    But due to missing " </TestFunction>" closure, we can never parse the XML results correctly...

    Can anyone explain the implementation of new TestSchedule.qml ? I presume we have incorrect usage which means the cleanuptestcase does not complete before we mark the test as done.

    jsulmJ 1 Reply Last reply
    0
    • J jmcd

      Hello.

      We are currently upgrading from QT5.15 to QT6.7 and have noticed that due to some changes in TestCase.qml and new TestSchedule.qml , it appears XML testresults output are never correctly closed.

      E.g. after running simple app startup test:

      <TestCase name="UITest">
        <Environment>
          <QtVersion>6.7.2</QtVersion>
          <QtBuild>Qt 6.7.2</QtBuild>
          <QTestVersion>6.7.2</QTestVersion>
        </Environment>
        <TestFunction name="Null test::initTestCase">
          <Incident type="pass" file="" line="0" />
          <Duration msecs="28.9662"/>
        </TestFunction>
      <TestFunction name="Null test::test_WaitForStart">
          <Message type="qinfo" file="" line="0">
              <Description><![CDATA[qml: Waited for app to start]]></Description>
           </Message>
          <Incident type="pass" file="" line="0" />
          <Duration msecs="1265.11"/>
        </TestFunction>
       <TestFunction name="Null test::cleanupTestCase">
        <Duration msecs="4071.77"/>
      </TestCase>
      

      But due to missing " </TestFunction>" closure, we can never parse the XML results correctly...

      Can anyone explain the implementation of new TestSchedule.qml ? I presume we have incorrect usage which means the cleanuptestcase does not complete before we mark the test as done.

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @jmcd Looks like a bug to me. You should report it on the Qt bug tracker.

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      1

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved