-
Notifications
You must be signed in to change notification settings - Fork 288
Conversation
…-rat-tests * origin/release/2.1.x: change of prefix fixing tests after refactoring Fix Screenshot for negative Testresult Clear ChildViewController before adding something new that shoudl replace it. moved to publisher because of reactivity changes after feedback changes for voice over adding strings changes after testing missing semi colon fix adding prefix for voice over
…-rat-tests * origin/release/2.1.x: (31 commits) add new tests log text change move a code piece to the next step prevent package download if trace warning metadata empty Bump to next Version: 2.1.0.11 Uh a rare double Bump 🤯 Bump Version prevent invoking quickactions tests in iOS < 13 + some code improvements [INTERNAL] Translation delivery: commit by LX Lab Add comments Move keys submitted to outer scope Also set positive test result shown if keys were submitted, as in previous versions (< 2.1) that value was reset on submission and we now keep it set to true until the test is deleted consider safe area Migrate to positive test result if positive test result was shown or keys submitted [INTERNAL] Translation delivery: commit by LX Lab Fix indentation Schedule warn others notifications if consent is NOT given Bump Version add missing framework imports Version Bump to 2.1.0.7 ...
@@ -35,7 +35,7 @@ class HomeTestResultCellModel { | |||
@OpenCombine.Published var isActivityIndicatorHidden: Bool = false | |||
@OpenCombine.Published var isUserInteractionEnabled: Bool = false | |||
@OpenCombine.Published var isCellTappable: Bool = true | |||
@OpenCombine.Published var accessibilityIdentifier: String! = AccessibilityIdentifiers.Home.submitCardButton | |||
@OpenCombine.Published var accessibilityIdentifier: String! = "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to have a generic identifier at least? So we could test for something like: XCTAssertFalse(app.cells['shouldNotExist'].exists)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting idea, I added it :)
positiveTestResultWasShown: UserDefaults.standard.string(forKey: "pcrPositiveTestResultWasShown") == "YES", | ||
isSubmissionConsentGiven: UserDefaults.standard.string(forKey: "isPCRSubmissionConsentGiven") == "YES", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be cool to have the strings as static constants (and later stored similar to the AppStrings). This could help to keep track on all these parameters and launch arguments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like that suggestion. That is something I would like to add to the refactoring/enhancement ticket for the exposure submission UI tests that we were just talking about.
Description
Adds and repairs unit and UI tests.
Link to Jira
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-6392