-
Updated
Mar 1, 2022 - JavaScript
bdd
Here are 1,389 public repositories matching this topic...
-
Updated
Mar 2, 2022 - JavaScript
-
Updated
Mar 1, 2022 - JavaScript
Hi,
As the XML.Get Element, XML.Set Element Text accept source to be "a path to an XML file, a string containing XML, or an already parsed XML element."
According to documentation, XML.Set Elements Text works like XML.Set Element Text.
But I figured out it ONLY accepts parsed XML. It fails if you supply a path to an XML file.
So you can do
${out} XML.Set Element
-
Updated
Mar 3, 2022 - Java
-
Updated
Feb 26, 2022 - Go
-
Updated
Feb 28, 2022 - PHP
-
Updated
Feb 28, 2022 - Swift
-
Updated
Jan 31, 2022 - PHP
-
Updated
Feb 23, 2022 - Go
-
Updated
Oct 29, 2019 - JavaScript
-
Updated
Mar 1, 2022 - C#
-
Updated
Dec 29, 2020 - Python
-
Updated
Mar 1, 2022 - Python
Summary
The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a
-
Updated
Feb 3, 2022 - JavaScript
-
Updated
Feb 1, 2022 - C++
-
Updated
Sep 10, 2021
-
Updated
Mar 3, 2022 - TypeScript
-
Updated
May 10, 2021 - JavaScript
-
Updated
Feb 25, 2022 - TypeScript
-
Updated
Dec 24, 2021 - Gherkin
Improve this page
Add a description, image, and links to the bdd topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the bdd topic, visit your repo's landing page and select "manage topics."
Describe the bug
When compiler flags are such that __FILE__ macro is replaced with a relative file path (on MSVC no /Z7, /Zi or /ZI and no /FC) then it might be replaced with just a filename with no path separators. In this case tags for tests with --filenames-as-tags do not contain '#' symbol.
The bug is present in the 2.x branch, but not in the main branch where the relevant code has