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

[QA] Cycle 2: Feature testing for reCAPCTHA #201

Closed
9 tasks
sdzhepa opened this issue Apr 9, 2020 · 5 comments
Closed
9 tasks

[QA] Cycle 2: Feature testing for reCAPCTHA #201

sdzhepa opened this issue Apr 9, 2020 · 5 comments
Assignees
Labels
Component: Google reCAPTCHA Issues and Pull Requests related to reCAPTCHA should be marked with this label

Comments

@sdzhepa
Copy link
Contributor

sdzhepa commented Apr 9, 2020

Description and purposes

Code version information:

On the starting day we used next commits and branch

Magento editions for test-case execution:

1. Magento Commerce(EE)
-- The main env for full testing
-- Prepared Cloud instance with sample data
-- Should be executed all test-cases that we have. (exception could be only for specific cases that not possible to execute due to Cloud Env)

2. Magento Open Source(CE)
-- Additional env for execution(on local machine). Install using Metapackage Installation Guide
-- Should contains only the most critical cases e.g. Checkout Flow etc
-- Here should be executed tests that not possible to do on EE due to limitation on Cloud env
-- All found issues on EE should be checked on CE before reporting

Workflow and testing process:

Should start in the next order:

  1. Cycle related to Magento Commerce(EE) Cloud.
  2. Cycle related to Magento Open Source(CE) Local
  3. Cycle related to cases/user flows in different browser

Bug reporting:

  • Each found bug should be reverified on CE local env. To be sure is it env/edition specific or not
  • Each bug should be reported as an issue in this repository. It should have labels: 'Component: Google reCAPCTHA' and 'bug'

Failed/Skipped/Blocked test cases:

  • Each FAILED test-case should have a link to the created issue in the "Execution" section and additional comment if required
  • Each SKIPPED/BLOCKED test-case should have a clear comment with explanation in the "Execution" section

Bug triaging and fixing

  • Each newly created bug should be triaged. Discuss and understand its priority/severity. Must be fixed now or can be postponed
  • Only after triage and decision, devs can start progress on it.
  • Each fixed bug must be tested in the scope of Pull Request.
  • Based on the number of new bugs and specific will be decided do we need additional Test Run or not

Test Cycle information, links, and Additional details

Magento Commerce Cloud

Name: Cycle 2: reCAPCTHA testing on Magneto Cloud

Additional testing scope:

Magento Open Source(CE) Local

Name: Cycle 2: reCAPCTHA testing on Magneto Open Source

Additional testing scope:

Browser specific testing (Google Chrome, Mozilla Firefox, IE11/Edge)

Name: Cycle 2: reCAPCTHA testing on Magneto Open Source

Additional testing scope:

@sdzhepa sdzhepa added the Component: Google reCAPTCHA Issues and Pull Requests related to reCAPTCHA should be marked with this label label Apr 9, 2020
@sdzhepa sdzhepa self-assigned this Apr 9, 2020
@sdzhepa
Copy link
Contributor Author

sdzhepa commented Apr 10, 2020

Testing report on Apr 10 2020

Start testing.
No new bugs found

Details

  1. Cycle related to Magento Commerce(EE) Cloud.
  • Total test cases: 70
  • Passed: 20
  • Failed: 0
  • Skipped 0
  1. Cycle related to Magento Open Source(CE) Local
  • Total test cases: 38
  • Passed: 11
  • Failed: 0
  • Skipped 0
  1. Cycle related to cases/user flows in different browser
  • Total test cases: 21
  • Passed: 0
  • Failed: 0
  • Skipped 0

@sdzhepa
Copy link
Contributor Author

sdzhepa commented Apr 14, 2020

Testing report on Apr 14 2020 (3rd day of testing)

Found Bugs

Details

  1. Cycle related to Magento Commerce(EE) Cloud.
  • Total test cases: 70
  • Passed: 51
  • Failed: 2
  • Skipped: 5 List
  1. Cycle related to Magento Open Source(CE) Local
  • Total test cases: 38
  • Passed: 21
  • Failed: 0
  • Skipped 0
  1. Cycle related to cases/user flows in different browser
  • Total test cases: 21 per each browser(FireFox, Chrome, IE11, Endge)

FireFox

  • Passed: 0
  • Failed: 0

Chrome

  • Passed: 13
  • Failed: 0

IE 11

  • Passed: 0
  • Failed: 0

Edge

  • Passed: 0
  • Failed: 0

@sdzhepa
Copy link
Contributor Author

sdzhepa commented Apr 15, 2020

Testing report on Apr 15, 2020 (4rd day of testing)

No new bugs found

All Found Bugs

Details

  1. Cycle related to Magento Commerce(EE) Cloud.
  • Total test cases: 70
  • Passed: 56
  • Failed: 3
  • Skipped: 7 List
  1. DONE Cycle related to Magento Open Source(CE) Local
  • Total test cases: 38
  • Passed: 38
  • Failed: 0
  • Skipped 0
  1. Cycle related to cases/user flows in different browser
  • Total test cases: 21 per each browser(Firefox, Chrome, IE11, Edge)

FireFox

  • Passed: 14
  • Failed: 0

Chrome

  • Passed: 14
  • Failed: 0

IE 11

  • Passed: 0
  • Failed: 0

Edge

  • Passed: 0
  • Failed: 0

@engcom-Delta
Copy link

engcom-Delta commented Apr 16, 2020

Results for addional testing scope:

Magento Commerce Cloud

Name: Cycle 2: reCAPCTHA testing on Magneto Cloud

Additional testing scope:

Magento Open Source(CE) Local

Name: Cycle 2: reCAPCTHA testing on Magneto Open Source

Additional testing scope:

Browser specific testing (Google Chrome, Mozilla Firefox, IE11/Edge)

Name: Cycle 2: reCAPCTHA testing on Magneto Open Source

Additional testing scope:

@sdzhepa
Copy link
Contributor Author

sdzhepa commented Apr 16, 2020

Testing report on Apr 16, 2020 (5th day of testing)

All planned test cycles were executed.
Testing is done

All Found Bugs

Details

  1. DONE Cycle related to Magento Commerce(EE) Cloud.
  • Total test cases: 70
  • Passed: 60
  • Failed: 3
  • Skipped: 7 List
  1. DONE Cycle related to Magento Open Source(CE) Local
  • Total test cases: 38
  • Passed: 38
  • Failed: 0
  • Skipped 0
  1. Cycle related to cases/user flows in different browser
  • Total test cases: 21 per each browser(Firefox, Chrome, IE11, Edge)

FireFox

  • Passed: 14
  • Failed: 0

Chrome

  • Passed: 14
  • Failed: 0

IE 11

  • Passed: 14
  • Failed: 0

Edge

  • Passed: 14
  • Failed: 0
  1. DONE Addition testing scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Google reCAPTCHA Issues and Pull Requests related to reCAPTCHA should be marked with this label
Projects
None yet
Development

No branches or pull requests

2 participants