• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Tests
    • 7
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Need the abilty to view the junit test logs

            [BAM-782] Ability to view the junit test logs

            pBogey added a comment -

            Disappointing to end up here after searching for why Bamboo doesn't display system-out info. Seems like such a simple and basic thing to do.

            pBogey added a comment - Disappointing to end up here after searching for why Bamboo doesn't display system-out info. Seems like such a simple and basic thing to do.

            Atlassian Update – [16 April 2019]

            Hi everyone,

            Thank you for your interest in this issue.

            While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future.

            We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including:

            1. Performance and stability improvements
            2. Providing building blocks for High Availability and Disaster Recovery solutions
            3. Improving permission system
            4. Allowing per-project allocation of resources
            5. Improving Bitbucket Server and Jira integrations

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

            To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Bamboo Team

            Krystian Brazulewicz added a comment - Atlassian Update – [16 April 2019] Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including: Performance and stability improvements Providing building blocks for High Availability and Disaster Recovery solutions Improving permission system Allowing per-project allocation of resources Improving Bitbucket Server and Jira integrations We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Bamboo Team

            Am I reading this right, has this issue been open for over 10 years? I stumbled upon it, because I would like to display successful test results, not only failures and errors.

            Saša Gaberšek added a comment - Am I reading this right, has this issue been open for over 10 years? I stumbled upon it, because I would like to display successful test results, not only failures and errors.

            The fact that this has been open for so long is troublesome with respect to Atlassian's commitment to improving Bamboo...

            Chad Hutchins added a comment - The fact that this has been open for so long is troublesome with respect to Atlassian's commitment to improving Bamboo...

            +1 for this improvement.

            alexchistyakov added a comment - +1 for this improvement.

            WestonM added a comment -

            Why has this not been implemented? Is there a good workaround for this?

            WestonM added a comment - Why has this not been implemented? Is there a good workaround for this?

            Inbar Rose added a comment -

            Please implement this. It is such a drag not having this, or at least provide a different test parser solution.

            Inbar Rose added a comment - Please implement this. It is such a drag not having this, or at least provide a different test parser solution.

            I just recently needed to debug why a test that passes on local machine, suddenly fails on Bamboo. The only way I could think of tracing the problem was by adding System.out.println output to the test setup.

            Unfortunately, this did not do anything in my vase, as it seems that Bamboo is just ignoring output to standard out.

            Roland Tepp added a comment - I just recently needed to debug why a test that passes on local machine, suddenly fails on Bamboo. The only way I could think of tracing the problem was by adding System.out.println output to the test setup. Unfortunately, this did not do anything in my vase, as it seems that Bamboo is just ignoring output to standard out.

            The Bamboo JUnit Parser produces a report which does not include all the information available from the underlying JUnit results files.

            JUnit produces an xml file with test results, and this is what is parsed by the Bamboo JUnit parser. The parser displays items from the <testcase> xml nodes, along with any associated <error> node for that testcase. However it does not include info from the <system-out> or <system-err> nodes in the JUnit xml results files. These nodes contain captures of output of the Standard Out and Standard Error logs.

            Without the <system-out> and <system-err> nodes, the logging generated by the tests may be lost.

            Other CI tools provide access to this information. For example, a Jenkins and the Ant "junitreport" task produce an html report that contains links to these sections.

            Impact: Bamboo's JUnit parser produces a report with missing data. This makes the Bamboo's JUnit integration much less useful than it could be.

            Workaround: since Bamboo's JUnit parser does not automatically capture this data, I have manually copied the JUnit results files as Artifacts in the Bamboo job.

            This workaround is not ideal because these results files are plain xml and require additional processing to extract the logs. Also these raw xml files can be very large and are not really suitable for display or retrieval over Http. A server-generated report based on these files is preferable so the data can be paged etc. and made more suitable for retrieval and display in a web browser.

            Michael Hartman added a comment - The Bamboo JUnit Parser produces a report which does not include all the information available from the underlying JUnit results files. JUnit produces an xml file with test results, and this is what is parsed by the Bamboo JUnit parser. The parser displays items from the <testcase> xml nodes, along with any associated <error> node for that testcase. However it does not include info from the <system-out> or <system-err> nodes in the JUnit xml results files. These nodes contain captures of output of the Standard Out and Standard Error logs. Without the <system-out> and <system-err> nodes, the logging generated by the tests may be lost. Other CI tools provide access to this information. For example, a Jenkins and the Ant "junitreport" task produce an html report that contains links to these sections. Impact: Bamboo's JUnit parser produces a report with missing data. This makes the Bamboo's JUnit integration much less useful than it could be. Workaround: since Bamboo's JUnit parser does not automatically capture this data, I have manually copied the JUnit results files as Artifacts in the Bamboo job. This workaround is not ideal because these results files are plain xml and require additional processing to extract the logs. Also these raw xml files can be very large and are not really suitable for display or retrieval over Http. A server-generated report based on these files is preferable so the data can be paged etc. and made more suitable for retrieval and display in a web browser.

            Hudson/Jenkins and Ant/junitreport both have this capability. Would like to see this in Bamboo as well.

            David Mahoney added a comment - Hudson/Jenkins and Ant/junitreport both have this capability. Would like to see this in Bamboo as well.

              Unassigned Unassigned
              3a88b175bc2e Daniel Woodhams
              Votes:
              29 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated: