Skip to content
New issue

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

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

Already on GitHub? # to your account

IBX-1552 As a QA I want spike test coverage for deep links #2023

Merged
merged 1 commit into from
Jan 21, 2022

Conversation

piotrbisaga
Copy link
Contributor

Question Answer
Tickets https://issues.ibexa.co/browse/IBX-1552
Bug fix? no
New feature? no
BC breaks? no
Tests pass? yes/no
Doc needed? no
License GPL-2.0

Checklist:

  • Coding standards ($ composer fix-cs)
  • Ready for Code Review

@@ -17,3 +17,10 @@ Feature: Verify that Admin Panel is available only for authenticated users
Given I open Login page in admin SiteAccess
When I log in as admin with password notpublish
Then I should be on Login page

@javascript
Scenario: Should be redirected to the same page in back office after relogin
Copy link
Member

Choose a reason for hiding this comment

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

I don't think the application behaves like that and it's a different Scenario than what's in https://issues.ibexa.co/browse/EZP-26238

I'd start with the ticket description:

For example, in eZ Publish 5.4.7, if you point your browser to:
http://example.com/ezdemo_site_admin/Tests/Article-1
...you will get to that page after login. In eZ Studio that no longer happens, you always get re-directed to the dashboard after login.

which we then could convert into a Scenario like this:

Given I open back office deep link page X
And I login as <USER>
Then I should be on Page X

Which we will have to adjust and reuse our existing Steps.

I think that there are two issues with the current Scenario:

  1. It uses logout, which https://issues.ibexa.co/browse/EZP-26238 does not mention at all - imho it's best to focus on the initial Scenario first
  2. It uses logout, but it never logs in before that - which seems incorrect

@piotrbisaga piotrbisaga force-pushed the ibx-1552-spike-test-coverage-for-deep-links branch from 6acf65e to 9ed74f7 Compare January 17, 2022 13:15
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link
Member

@micszo micszo left a comment

Choose a reason for hiding this comment

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

LGTM. 🙂

@piotrbisaga piotrbisaga marked this pull request as ready for review January 17, 2022 15:39
@micszo micszo changed the title [WIP] IBX-1552 As a QA I want spike test coverage for deep links IBX-1552 As a QA I want spike test coverage for deep links Jan 21, 2022
@micszo micszo merged commit 411c4b2 into 2.3 Jan 21, 2022
@micszo micszo deleted the ibx-1552-spike-test-coverage-for-deep-links branch January 21, 2022 11:57
# for free to join this conversation on GitHub. Already have an account? # to comment
Development

Successfully merging this pull request may close these issues.

5 participants