Remove Files supports patterns too:
Remove Files ${path}/*.txt
Sent from my mobile.
--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.
To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at https://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.
Remove Files supports patterns too:
Remove Files ${path}/*.txt
Sent from my mobile.
23.2.2016 6.19 ip. "Kevin O." <korm...@gmail.com> kirjoitti:
--Try this:@{txt files}= List Directory ${path} *.txt absolute=${True}Remove Files @{txt files}
On Thursday, February 18, 2016 at 6:30:39 PM UTC-6, M Hanes wrote:Hi all,
I have a test scenario where I create a .txt file in a network folder directory, but before creating this file I need to make sure there are no other .txt files in the directory (there may be other test files from people who are running manual tests and then they left their test file in the directory when they were finished.) So I need a step that will check for any .txt file that may have been left behind, and then delete the file... or just delete any file(s) that it finds in the directory. I would use the "Empty Directory" keyword, but that deletes all sub-directories as well, and I do have a couple of sub-directories within the folder that I can't delete or it will cause big problems.
Does anyone have suggestions on how I could do this?
Thanks!
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.