Concordion Presenter Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID concordionpresenter Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
0.7 (archives)
Aug 13, 2011
1.398
Source Code
Issue Tracking
Pull Requests
Maintainer(s)
GitHub
Open Issues
Pull Requests
Rob Johnston (id: rjohnst)
Usage Installations 2014-May 117
2014-Jun 103
2014-Jul 106
2014-Aug 108
2014-Sep 105
2014-Oct 110
2014-Nov 107
2014-Dec 107
2015-Jan 103
2015-Feb 110
2015-Mar 113
2015-Apr 113

This plugin publishes Concordion test reports for each build, and is based somewhat on the WebTest Presenter Plugin.

Usage

Configuration:

Project page:

Build page:

TODO

  • Option to create index page for test reports
  • Junit-esque integration (pass/fail graph, failed tests link to specifications)

Version History

Version 0.7 (2011-08-13)

  • Reworked archiving code and added some diagnostics
  • Updated for Jenkins

Version 0.6 (2010-07-06)

  • Initial release (after a few mix-ups with publishing releases and group ids)

Labels

plugin-report plugin-report Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 07, 2010

    Nigel Charman says:

    Hi Rob, Does this plugin provide any advantage over using the HTML Publisher pl...

    Hi Rob,

    Does this plugin provide any advantage over using the HTML Publisher plugin for Concordion reports?

    1. Jul 07, 2010

      Rob Johnston says:

      Hi Nigel Not really, except that the word "Concordion" now shows up in the list...

      Hi Nigel

      Not really, except that the word "Concordion" now shows up in the list of available plugins

  2. Jul 16, 2010

    Allan says:

    Hi Rob I get a 404 error when I try to access the 'latest concordion results' l...

    Hi Rob

    I get a 404 error when I try to access the 'latest concordion results' link.   

    I've set the 'Concordion report location' to be the directory where the concordion results html is generated to - I'm guessing that's what it should be pointing to.

    Do you know what I've done wrong?

    1. Jul 19, 2010

      Rob Johnston says:

      Hi Allan That will happen if the results for the "last completed" build aren't ...

      Hi Allan

      That will happen if the results for the "last completed" build aren't parsed by the plugin - so the build might be failing and the results aren't generated. What appears in the console?

      This is also an issue, since that link should really point to the last set of results that the plugin picked up

      1. Aug 01, 2010

        Allan says:

        Hi Rob Thanks for your answer :-) My Concordion output directory is 'trunk/dir...

        Hi Rob

        Thanks for your answer :-)

        My Concordion output directory is 'trunk/direct-tv-service-module/build/spec-results' and the reports are successfully generated here. The build is successful and I get this message in the console output:

        BUILD SUCCESSFUL
        Total time: 3 seconds
        Archiving Concordion test report...
        Archiving report from /root/.hudson/jobs/Specification Tests/workspace/trunk/direct-tv-service-module/build/spec-results to /root/.hudson/jobs/Specification Tests/builds/2010-08-01_13-11-32/concordion

        If I look on the Hudson server I can see the html files have been moved correctly to:

        builds/2010-08-01_13-11-32/concordion

        and I can see the moved html files in there.

        This is the result of an 'ls -R' in that directory:

        ./bootstrap:
        OnAFreshInstallTheApplicationShouldStoreADefaultSetOfPropertiesInAFileInTheUsersHomeDirectorySpec.html
        ./fileprocessing:
        ProcessingANewlyArrivedContentFileAndMeatadataFileSpec.html
        ./image:
        concordion-logo.png

        However I still get a 404 if I click on the concordion reports link in Hudson. :-(

        Do you know what I have done wrong?

        1. Aug 11, 2010

          Allan says:

          I've just answered my own question The concordion tests need their own index.h...

          I've just answered my own question

          The concordion tests need their own index.html to be put in the root of the concordion output directory.

          Do this and it works perfectly.

          Allan

          1. Aug 16, 2010

            Rob Johnston says:

            Hi Allan Yes, that'll do it

            Hi Allan

            Yes, that'll do it

          2. Mar 02, 2011

            larrycai says:

            So who is responsible to generate index.html this plugin, or concordion test ca...

            So who is responsible to generate index.html

            this plugin, or concordion test case (special configuration) or own scripts ?

            1. Mar 02, 2011

              Rob Johnston says:

              From what I've seen, it's your own scripts. We perform some post-processing on t...

              From what I've seen, it's your own scripts. We perform some post-processing on the concordion output to create an index.html that links to each of the concordion reports, I'm assuming that's what Allan's done as well.