chore: adding tags to the UITests - WPB-20997

[findms]

WPB-20997 [iOS/QA] Explore Tags in XCTest

---

Summary

Briefly describe about this PR changes.

• Added configuration in the env variable to run critical tests if test name has word critical
  Configuration for critical test run added so basically it check if test name has critical(ignore casing) then running critical testplan will run all the tests which has critical word, if running normal configuration(as before) it will run all tests.

---

Testing

Describe how to verify the changes locally. Attach screenshots of local execution if relevant.

tests name updated with critical like this

On running test using command bundle exec fastlane run_uitests configuration:UITest-critical , only test with critical word will run not others.

Additional Information

any more info, add here.

How to run?
To run tests marked with tags critical here is the command:
bundle exec fastlane run_uitests configuration:UITest-critical

if configuration is not being passed, it will run all tests as regression.
bundle exec fastlane run_uitests

[github-actions]

Test Results

1 883 tests   1 856 ✅  2m 4s ⏱️
  301 suites     27 💤
    1 files        0 ❌

Results for commit fde932d.

♻️ This comment has been updated with latest results.

Summary: workflow run #23191605547
Allure report (download zip): html-report-28586-chore_explore-tags-in-uitest

[netbe]

interesting way to use kind of "tags" in XCTest as it would be in SwiftTesting. For our usecase, I wonder if it's worth it to have this rather to rely on a specific testplan that would contain the critical tests: the same way we have security tests.

what do you think @johnxnguyen ?

[johnxnguyen]

interesting way to use kind of "tags" in XCTest as it would be in SwiftTesting. For our usecase, I wonder if it's worth it to have this rather to rely on a specific testplan that would contain the critical tests: the same way we have security tests.

what do you think @johnxnguyen ?

@findms @netbe

It's a shame that you can't add tags to XCTest cases like can for Swift Testing as that would be the preferred approach. For me, the better solution for XCTests is to have specific test plans (note that a single test can be in multiple test plans) as this will make it easier for people to read and it aligns with what we currently do already. I'd be cautious about adding additional variations for organizing and running tests.

[github-actions]

This PR is stale because it has been open 30 days with no activity. Please update it or close it in case is not relevant anymore.

[netbe]

@findms should we close this? @johnxnguyen

[findms]

@netbe @johnxnguyen
I am going to revive this again as picked this task in discipline.

[sonarqubecloud]

Quality Gate passed

Issues
12 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud