Frequently Asked Questions about Concordion
This page shows the FAQ for C#. Click the toggle buttons above to choose other options.
- How do I automate web browser testing with Concordion?
- How does Concordion differ from Selenium?
- How do I automate my web service / database / desktop app / green screen / other app with Concordion?
- Does Concordion itself have active specifications?
- Who developed Concordion.NET?
- How is Concordion licensed?
- Is there a mailing list?
- Is there a twitter account?
- How do I report defects or submit enhancement requests?
- Where is the source code repository?
- How do I collaborate with development of Concordion?
- Why do I get the error “The target type doesn’t contain tests from a known test framework or a ‘Main’ method”?
- Why do I get the error “no specification extensions defined for: Concordion.NET.Internal.SpecificationConfig”?
- I’ve got a question that hasn’t been answered. How do I get further help?
How do I automate web browser testing with Concordion?
Concordion integrates well with Selenium WebDriver for specification and testing of web browser applications.
How does Concordion differ from Selenium?
Selenium is a test scripting tool for driving web browsers. Concordion is a specification tool and hides scripting activity inside Java fixture code. For tests that exercise the browser, we recommend Selenium WebDriver with Concordion.
How do I automate my web service / database / desktop app / green screen / other app with Concordion?
Concordion acts as a test runner and integrates with any .NET library to drive other interfaces.
Does Concordion itself have active specifications?
Yes, see the Concordion.NET specifications.
Who developed Concordion.NET?
Concordion (for Java) was originally developed by David Peterson. The idea was sparked by conversations with testers and developers, in particular Nat Pryce and Steve Freeman while working at Easynet (BSkyB) in 2006.
In 2013, Nigel Charman took over as project lead, having developed the Concordion extensions mechanism.
Version 2.0 of Concordion was released in 2016 by a team of contributors.
Concordion.NET was originally ported from the Java version by Jeffrey Cameron.
In 2013, ShaKaRee took over as project lead, and updated the code base. In 2016, ShaKaRee brought the code to parity with the Java version by cross-compiling it using IKVM.NET and performance tuning it to be faster than the previous natively compiled version.
Concordion has been ported and further extended by several other developers.
See the Concordion team.
How is Concordion licensed?
Concordion is licensed under the Apache License, v2.0.
See here for the license text.
Is there a mailing list?
Yes, on Google Groups. Join here.
We also have a developer list for discussing development of Concordion core and extension code.
Is there a twitter account?
How do I report defects or submit enhancement requests?
In Concordion.NET’s Issues List.
Where is the source code repository?
git clone https://github.com/concordion/concordion.net.git
How do I collaborate with development of Concordion?
Firstly, you should create an issue for your enhancement request.
Concordion uses a “Fork & Pull” model for collaborative development. If you have changes that you would like us to consider for introduction to Concordion, you will need to fork the repository, commit and push your changes to your forked project, and send us a pull request referencing the URL of the issue that you created.
Please note that, in order to keep Concordion clean and minimal, we consider all enhancement requests carefully. Should your enhancement not be appropriate for Concordion core, you may wish to package it as a Concordion extension.
Why do I get the error “The target type doesn’t contain tests from a known test framework or a ‘Main’ method”?
Possible causes are:
Concordion.NUnit.dllis not in the NUnit addins folder. See how to install the Concordion NUnit dll as a NUnit addin.
- An old version of
Concordion.NUnit.dllis in the NUnit addins folder. Download the latest version and install it as a NUnit addin.
- The attribute
[assembly: RequiredAddin("ConcordionNUnitAddin")]is not in the
AssemblyInfo.csfile of the project. See Assembly Info for further information.
Why do I get the error “no specification extensions defined for: Concordion.NET.Internal.SpecificationConfig”?
The Concordion.NET runner is unable to find a matching specification for the fixture. Possible causes are:
- The default namespace + path of the specification does not match the namespace of the fixture. See locating the specification for more details.
- The specification isn’t included in the DLL. You need to set the value “Embedded Resource” on the property “Build Action” to include the specification in the DLL.
I’ve got a question that hasn’t been answered. How do I get further help?
If you believe the question should be answered on this website, please raise a website issue.
For more general questions, start a discussion on our Google Group (see link below), or ask on Stack Overflow.