update docs

README.md

@@ -23,10 +23,10 @@ Learn more about `Maestro` [here](https://maestro.mobile.dev/)
     leaksdetector -processName $YOUR_APP_NAME -e $SUPPORTED_TESTING_FRAMEWORKS -d $PATH_TO_DANGER_FILE
 ```
 
-## Current support testing frameworks
+## Current testing frameworks
 
 - [Maestro](https://maestro.mobile.dev/) ✅
-- [XCUITest](https://developer.apple.com/documentation/xctest) (In progress ⚙️)
+- [XCUITest](https://developer.apple.com/documentation/xctest) (XCUITest is not supported. Read more [here](./Docs/XCUITests.md)) ❌
 
 ## How it works
 
@@ -40,11 +40,7 @@ Find more about `leaks` tool and `memgraph` [here](https://developer.apple.com/v
 ## Why I used Maestro?
 
 1. I need a testing tool which doesn't kill the program after the testing finished execution. And Maestro support that. Also Maestro is very easy to integrate & use.  
-2. I've tried to used XCUItest, which is really promissing. Based on this [WWDC video](https://developer.apple.com/videos/play/wwdc2021/10180/) from Apple, XCUITest even *allows us to capture the stacktrace where leaks occur & generate a memgraph*. However, I've tried to follow the video but Xcode didn't generate any memgraph.   
-
-    => I'm working on this.   
-
-    I've posted some questions on [swiftforum](https://forums.swift.org/t/xctest-doesnt-generate-memgraph-file-after-ui-test-finish-execution/67982) and [developer.apple](https://developer.apple.com/forums/thread/738659). If you have any ideas, feel free to reply on the threads
+2. XCUITest can not preserve running program after test execution. Read more at [here](./Docs/XCUITests.md) 
 
 ## How to support your testing frameworks