Skip to content

[QAE-456] Simple bolus calculator element updates #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 20 commits into from
Apr 22, 2025

Conversation

Foscottl-TP
Copy link
Contributor

Added multiple elements in support of the Simple Bolus Calculator test case automation

@Foscottl-TP Foscottl-TP requested a review from Petr-Zywczok April 9, 2025 08:30
@Foscottl-TP Foscottl-TP changed the title QAE-456 Simple bolus calculator element updates [QAE-456] Simple bolus calculator element updates Apr 9, 2025
Changed bolusEntryTextField so it will support SImple Bolus Calulator and Bolus screens.
Both Current Glucose and Bolus fields use the same identifier so rather than the default value determining the correct field, a supporting extension in Base Screen was added to help distinguish the the two.
This can be used for parsing similar situations in future test cases.
Changed bolusEntryTextField so it will support SImple Bolus Calulator and Bolus screens.
Both Current Glucose and Bolus fields use the same identifier so rather than the default value determining the correct field, a supporting extension in Base Screen was added to help distinguish the the two.
This can be used for parsing similar situations in future test cases.
HomeScreen push was updated before updating with current build. This is to undo the previous commit.
Changing the Label names to see if this will work in application rather than using the first/last match method
Testing again if the bolus and current glucose field can be separately defined other than dissmissablekeyboardtextfield.
Updated text field query for Current Glucose and Bolus elements
Yet another attempt to pull duplicate identifier fields
Buckled and just added accesibilityIdentifier to each element...
Added Action to  get the bolus field value. Needed for verifying if the value is reset when the current glucose field is edited.
@Foscottl-TP Foscottl-TP force-pushed the scott/QAE-456-SimpleBolusCalculator-MinandMaxGlucos branch from 1c9bcb8 to bc0011a Compare April 11, 2025 18:20
Updated to corrent naming conventions
Fixed the spacing formatting issue on a Base Screen function and changed the label of the glucose EntryOutOfRangeWarning to match an identifier already present.
What the summary says
Fixed incorrect field name
Used to support the optional in verification: "Then x field displays value x" (New Bolus steps addition)
Reverted Capitalization and added Carbohydrates
Removed element and verification because it is no longer used due to suggested change in LoopSupport
Copy link
Contributor

@Petr-Zywczok Petr-Zywczok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some formatting comments, the rest looks good.



public func getPumpPillValue() -> String { hudPumpPill.getValueSafe() }
public func getHudGlucosePill() -> String { hudGlucosePill.getValueSafe()}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
public func getHudGlucosePill() -> String { hudGlucosePill.getValueSafe()}
public func getHudGlucosePill() -> String { hudGlucosePill.getValueSafe() }

@@ -41,6 +52,7 @@ public final class BolusScreen: BaseScreen {
}

public func setBolusEntryTextField(value: String) { bolusEntryTextField.typeText(value) }
public func setCurrentGlucoseEntryTextField(value: String) { currentGlucoseEntryTextField.typeText(value)}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
public func setCurrentGlucoseEntryTextField(value: String) { currentGlucoseEntryTextField.typeText(value)}
public func setCurrentGlucoseEntryTextField(value: String) { currentGlucoseEntryTextField.typeText(value) }

@@ -25,9 +27,18 @@ public final class BolusScreen: BaseScreen {
public var getBolusActionButtonLabel: String { bolusActionButton.getLableSafe() }

public func tapCancelBolusButton() { bolusCancelButton.safeTap() }
public func tapCurrentGlucoseEntryTextField() {currentGlucoseEntryTextField.safeTap()}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
public func tapCurrentGlucoseEntryTextField() {currentGlucoseEntryTextField.safeTap()}
public func tapCurrentGlucoseEntryTextField() { currentGlucoseEntryTextField.safeTap() }

Comment on lines 15 to 17
private var currentGlucoseEntryTextField: XCUIElement { app.textFields["textField_CurrentGlucose"]}
private var bolusEntryTextField: XCUIElement { app.textFields["textField_Bolus"]}
private var carbohydratesTextField: XCUIElement { app.textFields["textField_Carbohydrates"]}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
private var currentGlucoseEntryTextField: XCUIElement { app.textFields["textField_CurrentGlucose"]}
private var bolusEntryTextField: XCUIElement { app.textFields["textField_Bolus"]}
private var carbohydratesTextField: XCUIElement { app.textFields["textField_Carbohydrates"]}
private var currentGlucoseEntryTextField: XCUIElement { app.textFields["textField_CurrentGlucose"] }
private var bolusEntryTextField: XCUIElement { app.textFields["textField_Bolus"] }
private var carbohydratesTextField: XCUIElement { app.textFields["textField_Carbohydrates"] }

Foscottl-TP and others added 3 commits April 22, 2025 10:27
Removed element and verification because it is no longer used due to suggested change in LoopSupport
@Foscottl-TP Foscottl-TP merged commit 9ef4e03 into main Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants