You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Working with openfasttrace and coverage.xml files in various programming languages is a pain. As OFT always gets a hickup when such an XML file is present and fails miserably.
My only solution is at the moment: delete all coverage.xml files before running oft.
As I like to run oft in intervals, to see which things I've implemented in near-realtime, just like the test driven development, which is run at intervals as often as possible.
Describe the solution you'd like
I would like to have the solution of ignoring file patterns. which can include all files possible.
Describe alternatives you've considered
An alternative would be that you have to state the xml files OFT should parse aswell, instead of parsing ANY xml file it finds.
Additional context
None, atm. If I would have time to contribute I would do this. But priorities do not permit this atm. When the level of pain raised high enough, then probably to be able to work fluently.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Working with openfasttrace and coverage.xml files in various programming languages is a pain. As OFT always gets a hickup when such an XML file is present and fails miserably.
My only solution is at the moment: delete all coverage.xml files before running oft.
As I like to run oft in intervals, to see which things I've implemented in near-realtime, just like the test driven development, which is run at intervals as often as possible.
Describe the solution you'd like
I would like to have the solution of ignoring file patterns. which can include all files possible.
Describe alternatives you've considered
An alternative would be that you have to state the xml files OFT should parse aswell, instead of parsing ANY xml file it finds.
Additional context
None, atm. If I would have time to contribute I would do this. But priorities do not permit this atm. When the level of pain raised high enough, then probably to be able to work fluently.
The text was updated successfully, but these errors were encountered: