Skip to content
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

First commit for Espresso test #462

Open
wants to merge 53 commits into
base: main
Choose a base branch
from
Open

First commit for Espresso test #462

wants to merge 53 commits into from

Conversation

SyedaGini
Copy link

@SyedaGini SyedaGini commented Jun 18, 2024

UI automation Test cases using Espresso

@SyedaGini SyedaGini added the automation automation label Jun 18, 2024
@SyedaGini SyedaGini self-assigned this Jun 18, 2024
Copy link
Contributor

@danicretu danicretu left a comment

Choose a reason for hiding this comment

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

Great work Syeda, thank you! I left a couple of comments, nothing big, mostly related to renaming and removing unused code.

Also, please take a look at the git commit template we use in the repository and use the agreed convention when committing:

ci(ui-automation): Add Espresso for GiniBankSDKExample

PM-89

@SyedaGini
Copy link
Author

@danicretu We've discussed the commit style for automation specifically and here is the reference for the structure of commit
image

@SyedaGini
Copy link
Author

Thanks @danicretu for your input.
I have incorporated your suggestion, please do review the changes whenever you've time.

Copy link
Contributor

@danicretu danicretu left a comment

Choose a reason for hiding this comment

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

Thank you for the changes, Syeda!

Copy link
Contributor

@a-szotyori a-szotyori left a comment

Choose a reason for hiding this comment

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

Great work, @SyedaGini! I still see some improvement potential though 🙈

Thank you for using the POM pattern! For the tests I would advise to apply these tips:

  • Explicitly state in the test method name what is tested. It's ok to have long test method names.
  • A test should generally assert one thing only at the end of the test. There can and will be exceptions, but as a rule of thumb try to assert only one thing at the end of the test.
  • Tests should be independent so that we can run one specific test without having to run x nr of other tests before it. Imagine we want to fix test30_... and then we would need to run the previous 29 tests each time we want to see if test 30 works or not...

@SyedaGini
Copy link
Author

@a-szotyori the requested changes are incorporated, thank you!

Copy link
Contributor

@a-szotyori a-szotyori left a comment

Choose a reason for hiding this comment

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

Thank you, Syeda! As discussed on Slack please don't merge it yet.

…indow`

The emulator won't start without `-no-window` on GitHub Action runners.

This reverts commit 2aea8c9.

PM-89
Copy link

sonarcloud bot commented Jul 16, 2024

SyedaGinii and others added 29 commits September 11, 2024 15:55
Added automation for No Result Screen
Added automation for Digital Invoice Screen
Added automation for File Import Error Screen
…ice)

Added automation for Edit Button on Digital Invoice Screen.
Copy link

sonarcloud bot commented Oct 23, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants