Release

https://cheitgroup.atlassian.net/projects/RT/versions/10349

Date

14 нояб. 2024 г.

Version

14.11 Release stage NA

Description

Contributors

Dasha RozhniatovskaViktoriia MalyshAnton LiakhYurii Tymchuk

Release

https://cheitgroup.atlassian.net/projects/RT/versions/10347

Date

12 нояб. 2024 г.

Version

11.11 Release stage NA

Description

Contributors

Yurii TymchukDasha RozhniatovskaAnton Liakh

Release

https://cheitgroup.atlassian.net/projects/RT/versions/10335

Date

4 нояб. 2024 г.

Version

04.11 Release stage NA

Description

Contributors

Yurii TymchukIhor BushtakovAnton LiakhDasha Rozhniatovska

01

Scenario: Job publication is inactive
Given a user opens an inactive job publication
When the system detects the job is no longer available
Then the system displays a modal with a notification: "This position is no longer open."

02

Scenario: Modal design
Given a user views the inactive job publication modal
When the modal appears
Then it displays a clear message, an illustration, and a link labeled "Back to homepage."

03

Scenario: Navigation to the homepage
Given the modal is displayed
When the user clicks "Back to homepage"
Then the system redirects them to the homepage.

04

Scenario: Responsive design
Given the modal is displayed
When the user accesses it on different devices
Then the modal adjusts to fit desktop, tablet, and mobile views.

05

Scenario: Accessibility compliance
Given the modal is displayed
When the user navigates using a screen reader
Then the content is read aloud, and navigation is possible using the keyboard.

06

Scenario: Notification visibility
Given a user interacts with an inactive job publication
When the modal appears
Then the background content is dimmed, and the modal is in focus.

07

Scenario: Explore other jobs
Given a user views the inactive job modal
When they close the modal
Then the user is shown a suggestion section with similar active jobs.

Date

03.12.2024

Members

Oleksii Fedorchuk Andrii Kupriianov Anton Poliakov Olexandr Tikan Yurii Tymchuk Viktoriia Malysh Anton Liakh Ihor Bushtakov Dasha Rozhniatovska Ivan Hodoniuk Roman Kliuiko

Link to the board

Retro Sprint 83 – https://ideaboardz.com/for/Rocken%20Sprint%2083/5433111

• Team

• Team Velocity

• Design mini lessons

• Communication in the team

• Demo, it is good to see how it fast implementing in the real product

• Less bugs of migrations

• Migration processes

• Demo from Design team

• FE+BE team work

• Notifications about deploy on stage

• Ticket assignments (to proper dev)

• possibility to move tickets from in QA to Done

• whole project

• Nuances of the domain industry

• optimizations approaches for development of tasks that divided to several team members

01

Scenario: Display email notification settings
Given: A user navigates to the "Email Notifications" tab within Profile Settings
When: The tab is open
Then: The user should see a list of notification options, including "RockenTalent Functional and Security Emails," "Process-Related Updates," "Application Updates," "Referral Updates," and "Birthday Congratulations."

02

Scenario: Toggle individual notification
Given: The user is on the "Email Notifications" page
When: The user toggles any of the options (e.g., "Process-Related Updates")
Then: The selected option should enable or disable, updating the user’s preferences immediately.

03

Scenario: Enable all notifications
Given: The user is on the "Email Notifications" page
When: They enable all available notification options
Then: All notifications should be set to the active state, indicating the user will receive emails for all updates.

04

Scenario: Disable all notifications except mandatory
Given: The user is on the "Email Notifications" page
When: They disable all optional notifications
Then: Only the "RockenTalent Functional and Security Emails" should remain active, as it is essential for account security and platform updates (password reset).

05

Scenario: Save notification preferences
Given: The user modifies their notification settings
When: They navigate away from the page
Then: The system should automatically save their preferences, retaining the changes for next logins.

06

OOS Scenario: Notification settings tooltip
Given: The user is on the "Email Notifications" page
When: They hover over any notification title
Then: A tooltip should appear providing additional information about the type of updates included in that notification category.

07

OOS Scenario: Reset to default notification settings
Given: The user has modified their notification preferences
When: They select "Reset to Default"
Then: All notification preferences should revert to the default state with "RockenTalent Functional and Security Emails" enabled and others based on the platform’s initial settings.

08

OOS Scenario: Accessibility of toggles
Given: The user is on the "Email Notifications" page
When: They navigate through the page using a keyboard or screen reader
Then: Each toggle should be accessible and clearly labeled for users

09

Scenario: Confirmation of changes
Given: The user changes any notification setting
When: They exit the "Email Notifications" section
Then: A brief confirmation message should appear, notifying the user that their preferences have been saved.

10

Scenario: Mobile-friendly display
Given: The user accesses "Email Notifications" on a mobile device
When: They view the list of notification options
Then: All toggles should be aligned and accessible without horizontal scrolling, ensuring a user-friendly mobile experience.

01

Scenario: Display full article content.
Given: I am on an individual blog article page.
Then: I see the article’s title, author, date, reading time, main image, and the full content with headings and paragraphs.

02

Scenario: Show related articles.
Given: I am on an individual blog article page.
Then: I see a sidebar or section titled "Articles similar to this" displaying articles related to the current topic.

03

Scenario: Subscription prompt.
Given: I am on an individual blog article page.
Then: I see a "Subscribe now to our newsletter" prompt at the bottom of the article, allowing me to subscribe for updates.

01

Scenario: Display latest articles.
Given: I am on the blog main list page.
Then: I see a section titled "Latest News" showing the latest blog articles with an image, title, author, date, and reading time.

02

Scenario: Display popular articles.
Given: I am on the blog main list page.
Then: I see a section titled "Popular Articles" displaying popular articles with similar layout as "Latest News".

03

Scenario: Display all articles.
Given: I am on the blog main list page.
Then: I see an "All Articles" section showing a grid of articles below the "Popular Articles" section with pagination (e.g., "Load more articles").

04

Scenario: Subscription prompt.
Given: I am on the blog main list page.
Then: I see a "Subscribe now to our newsletter" prompt encouraging me to subscribe to stay updated.

01

Scenario: Display tags section
Given: A user is on the Company Page
When: The page loads
Then: A tags section should be displayed beneath the main content, featuring tags such as "Partner companies," "For students," "Remote," and other relevant filters.

02

Scenario: Tag visibility
Given: The user scrolls through the Company Page
When: They reach the tags section
Then: All available tags should be visible and easy to identify.

03

Scenario: Interactive tags
Given: The tags section is displayed
When: The user clicks on a tag
Then: The system should apply the corresponding filter and redirect to a relevant filtered page for that tag.

04

Scenario: Mobile responsiveness
Given: The user views the tags section on a mobile device
When: They scroll to the section
Then: Tags should be displayed in a scrollable or compact layout, maintaining accessibility and visibility.

05

Scenario: Tag consistency
Given: A user visits different company pages
When: They view the tags section
Then: The same tags layout and style should be consistent across all pages.

06

OOS Scenario: Accessibility
Given: The tags section is displayed
When: A user navigates using a keyboard or screen reader
Then: Each tag should be accessible and selectable via keyboard navigation and provide screen reader-friendly labels.

07

Scenario: Loading tags
Given: The user opens the Company Page
When: The tags section loads
Then: The tags should load simultaneously with the rest of the page content, without delay.