-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
concordion:run does not seem to work #14
Comments
To get it working with Concordion.NET, you need to utilize the default Concordion.NET test runner by using the parameter run="concordion.net" instead of run="concordion" Probably you need to provide the relative path to the sub specification you are trying to run. Thus, it could be that you need to adapt href="DefaultValue.html" to something like href="path/to/sub/spec/DefaultValue.html" Please find additional information about the run command in the specifications of Concordion.NET: |
@ShaKaRee I tried |
Thank you for reporting this bug. It is due to the fact that the concordion.net default runner is set while loading the configuration. As quick fix I am attaching a new Concordion.NET.dll that should fix this problem. |
@ShaKaRee Yeah! Works better now. Is it possible to update the NuGet package so everyone could have the fix? Thanks for your help by the way. |
Yes, I will prepare a new release of Concordion.NET so that the NuGet package can be updated. @Odonno |
Yeah. I can give you some feedback if that could be helpful. I recently discovered Concordion last year, reading a book about the implementation of Lean in softwares. In one part of this book, they talked about BDD and how they used it. They were using Concordion with java and clearly I did not know there was a BDD framework that uses HTML or Markdown as a guide to write specifications. That was a aha moment! So, I wanted to experiment this framework and I waited for the right side project to work with. Of course, I am more familiar with C#/JavaScript/TypeScript languages so the only option left was C#, even if the framework feels not as complete as the java implementation, like I saw in the docs of the website. From the first week of this year, I started to write a NuGet package where almost every test cases should be written in HTML and the implementation should follow in C#, in a TDD/BDD way. I found it a little hard to start at first because I was expecting a very simple tooling : using Visual Studio Test and auto generation of tests/files after build but there were more frictions than I expected : installing NuGet package + NUnit package + NUnitTestAdapter package. I am using NUnit v2.6.4 cause I read somewhere >= v3 is not supported. And then I needed to understand the differences between the use of the base class Well, now the configuration was set up, I started to add HTML file + fixtures/tests + C# code in my library. From this part, everything is really cool, it feels like magic. Only one thing that bothers me sometimes when I think how this framework can be more awesome and it's about the HTML/MD files. At first, it was a little bit difficult to locate the generated HTML files from the tests. By looking deeply in the docs website, I managed to find them but I realised it could be really good to :
Well, I think that's it. Like you saw, I am not really familiar with the framework at the moment but it does what it says and that's what is the more important : write your specs, write your code, feel free to conitnue by adding more specs and by improving the code. If there was anything I did wrong, please tell me so I can change things sooner than later. Hope it can help you. |
Hi, |
I read About the BaseOutputDirectory, I see you can set an absolute path (using C:/) but what if I want to put a relative path? About generating a local website for the specs, it is not mandatory, But, I can share it with you. I mean having a (possibly nodejs) project that :
|
Yes, you can use also a relative path as configuration of the BaseOutputDirectory. |
@Odonno |
I am trying to write a library using a Concordion spec project and I recently splitted some specification files (HTML + CS) into multiple files. Everything worked fine.
Then, I wanted to use the indexes feature of Concordion that give me a glimpse if another spec file succeed or failed from the current file. I figured I need to use the
concordion:run
property but here is the result I get :I can assure you the class and the spec files are at the respective location.. The class is using the right namespace too.
The text was updated successfully, but these errors were encountered: