robotframework
Support embedding Text test cases into Markdown files
Many source control systems including bitbucket support markdown natively. Adding markdown syntax will be much helpful.
Markdown is supported in Visual Studio Team Services, Team Foundation Server and Bitbucket. There is no support for reStructuredText. This will be more helpful to add "Acceptance Documentations" available naturally. Without which it adds additional dependencies to make documentations and scripts available as HTML, PDF documents.
@vairamsvsjdo Are talking about saving robot test as MarkDown (.md) files instead of .robot or .txt?
You may have a look in RobotFramework's Slack channel by following this link. There I have mentioned my experiment on that. I think I have not publish it on Github yet, but if there is interest I could do a pull request or provide the steps as a Gist.
EDIT: I put the steps into a Gist
@Tset-Noitamotua that is exactly I was looking for. @pekkaklarck please add this into robotframework support. It works excellent. I have about 50 test script files embedded with acceptance criteria documentations and all work perfect.
OK, you meant creating test cases in Markdown files similarly as you can create tests in reStructuredText files nowadays. I'm totally fine with that idea and, as @Tset-Noitamotua commented, there's already been discussion about that earlier on different forums. You could have also meant using Markdown when defining library documentation which is a valid proposal too.
What needs to be done to actually get the requested Markdown support into the framework is proving a pull request. The Gist by @Tset-Noitamotua is a good start but needs a little cleanup. A bigger task is creating tests and wring documentation. If there's anyone interested, please first take a look at the CONTRIBUTING.rst file in the project root. I'm willing to help here or on Slack too.
@pekkaklarck @Tset-Noitamotua bryan_oakley and @bassam.khouri changed this into a single feature by updating the issue name. and looking to add support for the following as separate features
Markdown support for Doc in libraries Support for HTML test cases
Better to have just one feature per issue. This issue covers adding support for test cases in MD files, supporting MD in library docs requires another issue. That is likely to be a bit more complicated feature to implement too.
PR #2621 looks pretty good. I need to look could it be included into 3.0.3.
RF 3.0.3 has been delayed a lot. Now we want it out ASAP and decided to only include bug fixes in it. I'll thus descope this enhancement to RF 3.1 which we plant to start developing right after RF 3.0.3 is out.
@vairamsvsjdo, do you still have interest to work with this issue? Getting this into RF 3.1 would be great.
@pekkaklarck Yes, will work on this next week. What is your timeline? I have few other tasks to take care in OSS next week.
What is the status of this one? I would like to pick it up again.
What needs to be done to get it into official release?