01

Scenario: Navigate using Anchor Links
Given I am viewing the "Personal Info" tab,
When I click on any anchor link (e.g., "General", "Personal", "About", etc.),
Then I should smoothly and quickly navigate to the corresponding section.

02

Scenario: Display General Section
Given I am viewing the "Personal Info" tab,
When I navigate to the "General" section,
Then I should see the candidate’s current salary, employment type, preferred working locations, and other general information.

03

Scenario: Display Personal Section
Given I am viewing the "Personal Info" tab,
When I navigate to the "Personal" section,
Then I should see the candidate’s gender, date of birth, nationality, work permits, address, phone number, email, marital status, and children details.

04

Scenario: Display About Section
Given I am viewing the "Personal Info" tab,
When I navigate to the "About" section,
Then I should see the candidate’s professional summary, including key strengths and hobbies.

05

Scenario: Display Hobbies Section
Given I am viewing the "Personal Info" tab,
When I navigate to the "Hobbies" section,
Then I should see a list of the candidate’s hobbies and personal interests.

06

OOS Scenario: Display External Links Section
Given I am viewing the "Personal Info" tab,
When I navigate to the "External Links" section,
Then I should see the candidate’s links to external platforms such as LinkedIn, Behance, etc., displayed for easy access.

Story 1.4.2.14. CRM. Profile view mode. Tab Personal. External links

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Scenario: Display profile header
Given the user is on the profile view mode page
When the page is loaded
Then the header should display the profile’s name, photo, and status

02

Scenario: Status change button
Given the user is viewing a profile
When the user clicks the "change status" button
Then the system should allow the user to update the status of the profile

03

Scenario: Rocken Talent indicator
Given the profile is part of Rocken Talent
When the user views the profile
Then an icon should indicate the profile’s inclusion in Rocken Talent

04

Scenario: Active search and active source indicators
Given the user is viewing a profile
When the page loads
Then the active search and active source checkboxes should be visible and indicate their current status

05

Scenario: Top 3 Info Cards arrangement
Given I am on the Profile page,
When I view the profile,
Then the top 3 info cards should display in the following order:
Left: Personal Information (gender, birthday, nationality, etc.),

Story 1.4.2.11. CRM. Profile view mode. Top left card

Middle: Search Information (desired salary, current job, etc.),

Story 1.4.2.12. CRM. Profile view mode. Top middle card

Right: Notes as the first tab, followed by Attachments, Activities, and Communication.

Story 1.4.2.13. CRM. Profile view mode. Top right card

01

Scenario: Display of action buttons
Given the user is viewing a profile in Profile View Mode
When the page loads
Then the following action buttons are displayed:
– Create Process
– Invite to RT
– interview invitation
– Open profile preview page
– Delete RT Profile
– Delete CRM Profile.

02

Scenario: Create Process functionality
Given the user clicks the Create Process button
When the action is initiated
Then a process creation workflow is opened, allowing the user to link the profile to a new process.

03

Scenario: Invite to RT functionality
Given the user clicks the Invite to RT button
When the action is initiated
Then the system sends an invitation to the candidate to join Rocken Talent.

04

Scenario: View Settings menu
Given the user clicks the View Settings button
When the action is initiated
Then a dropdown menu is displayed with options for managing the profile, including Delete RT Profile and Delete CRM Profile.

05

Scenario: Delete RT Profile
Given the user has the appropriate permissions
When they select Delete RT Profile
Then the system prompts for confirmation before removing the profile from Rocken Talent (soft delete).

Story 1.4.2.5. CRM. Talent Profile view mode. Delete RockenTalent Account

06

Scenario: Delete CRM Profile
Given the user has the appropriate permissions
When they select Delete CRM Profile
Then the system prompts for confirmation before permanently deleting the profile from the CRM.

07

Scenario: Permissions for delete actions
Given the user does not have the required permissions (not HoR, HoD, BM, Admin, owner of profile)
When they attempt to access Delete RT Profile or Delete CRM Profile
Then the system disables the options

01

Scenario: Opening the Filters panel
Given I am on the Profile List page
When I click on the "Filters" link
Then the filters panel should open on the right side of the screen, displaying filter options such as

1. Title / Titel

2. Keyword / Keyword

3. Status / Status

4. Search status / Status der Suche

5. Last status change / Letzte Statusänderung

6. Industry / Branchen

7. Category / Kategorien

8. Skill / Skill

9. Desired Salary (CHF / Year) / Gewünschtes Gehalt (CHF / Jahr)

10. Responsible / Verantwortlich

11. Location / Standort

12. Search radius / Suchradius

13. Language / Sprachen

14. Application Source / Bewerbungsquelle

15. Employment type / Art der Beschäftigung

16. Experience / Erfahrung

17. Workload / Arbeitspensum

18. Leading experience / Führungserfahrung NEW

19. Education / Ausbildung

20. Show profiles / Profile anzeigen

21. Market / Markt

02

Scenario: User interact with the filter panel
Given user in filter panel,
When clear/add/search some items
Then have common behaviour of the field described here: Story 1.0.12.5. CRM. Filter panel

https://api.staging.rockengroup.com/api-documentation-2000#/Profile/get_api_v1_profiles

01

Title

Scenario: User interact with the field
Given user in filter panel,
When search some items (role of candidate)
Then have common behaviour of the field described here: Story 1.0.12.6. CRM. Title field filter

titles[]

02

Keyword (moved to the list page)

Scenario: User applies a keyword filter.
Given the user enters a custom keyword,
When it is find info in any profile fields without suggestions
AND data matches with keyword ,
Then relevant results are displayed

Select type:

• multi select OOS

• multi tags

• search OOS

• suggestions OOS

• custom tags

keywords[]

Search by fields:

• profession' => 1.8,

• 'experience_titles',

• 'slug' => 2,

• 'phone' => 2,

• 'email' => 2,

• 'name' => 2,

• 'profession' => 1.8,

• 'experience_titles' => 1,

• 'experience_descriptions' => 1,

• 'experience_companies' => 1,

• 'interview_core_questions' => 1,

• 'industries_text' => 1,

• 'locations_text' => 1,

• 'skills_text' => 1.5,

• 'categories_text' => 1.3,

• 'responsible_text' => 1,

• 'responsible_unit_text' => 1,

02a

Scenario: Search for exactly matching keywords

Given the user is on the filter panel and enters the keyword “Some tags”

When the user submits custom tag

Then only results containing the exact phrase “Some tags” should be displayed, excluding partial matches or variations like “some” or “tags.”

02b

Scenario: Case-insensitive search

Given the user enters the keyword “Some tags” in any case (e.g., “some tags” or “SOME TAGS”)

When the search is performed

Then the results should include matches for the exact phrase “Some tags” regardless of letter casing.

03

Status

Scenario: User applies a status filter.
Given the user selects a status,
When the selection is made,
Then the results reflect the selected status.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

statuses[]

Available values:

• Unfinished / Unfinished

• New / New

• In Progress / In Progress

• Interview / Interview

• Rejection / Rejection

• Profile Creation: rejection / Profil Creation: rejection

• Rejection (Deletion) / Rejection (Deletion)

• Active / Active

• Offline / Offline

• Reapplied / Reapplied

04

Search Status

Scenario: User filters by Search status.
Given Search status exist,
When one is selected,
Then results match the selection.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

search_statuses[]

Available values:
Active Search / Aktive Suche
Passive Search / Passive Suche
Offline / Nicht auf der Suche

05

Last Status Change

Scenario: User applies a Last status change filter.
Given Last status field,
When select range of dates From-To,
Then results show last updated profiles in that range.

should be added to API by backend developer

06

Industry

Scenario: User applies an industry filter.
Given the user types an industry,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

07

Category

Scenario: User applies a category filter.
Given the user types a category,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

categories[]

08

Skill

Scenario: User applies a skill filter.
Given the user enters a skill,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

skills[]

09

Desired Salary (CHF / Year)

Scenario: User filters by desired salary.
Given the user inputs "From" and "To" values,
When valid,
Then results show jobs in the range.

salary[]

10

Responsible

Scenario: User applies a Responsible filter.
Given responsible options exist for this profile,
When one is selected,
Then results show jobs managed by the responsible.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

responsible[]

11

Location

Scenario: User applies a location filter.
Given the user enters a location (city),
When matched cities exist,
Then suggestions are displayed.

Select type:

• single select

• single tags

• search

• suggestions

• custom tags OOS

location

12

Search Radius

Scenario: User filters by search radius.
Given a numeric input field,
When a radius is entered,
Then results match the specified area that related to selected “Location“.

should be added to API by backend developer

13

Language

Scenario: User filters by language.
Given language options exist,
When one is selected
AND the order of languages should follow the specified sequence: Deutsch, Englisch, Französisch, Italienisch, and others alphabetically.
Then results reflect vacancies requiring that language.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

14

Application Source

Scenario: User applies a Application source filter.
Given application source options exist,
When several can be selected,
Then results show jobs based on selected application source.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

There is no specific list of sources, generated dynamically

15

Employment Type

Scenario: User filters by employment type.
Given available options,
When a type is selected,
Then results reflect the chosen type.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

16

Experience

Scenario: User filters by experience level.
Given experience levels,
When one or more levels are selected,
Then results show matching requirements.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

17

Workload

Scenario: User filters by workload.
Given "From" and "To" inputs exist,
When valid values are entered,
Then results match the range.

workload[]

18

Leading experience NEW

Scenario: User applies a leadership experience filter.
Given experience levels exist,
When one is selected,
Then relevant jobs are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

There is API: leading_experience
BUT using: Front Enum options

Options:

• None / Keine

• Professional guidance of employees / Fachliche Führung von Mitarbeitenden

• Management of project teams / Führung von Projektteams

• Personal leadership experience / Personelle Führungserfahrung

19

Education

Scenario: User applies a Education filter.
Given education options exist,
When several options can be selected,
Then results show jobs based on selected educations.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

Options:

• Master / Master (Hochschule)

• Bachelor / Bachelor (Hochschule)

• Diploma DAS / Diploma of Advanced Studies DAS

• Gymnasium / Gymnasium

• Federal Professional Certificate / Eidg. Fachausweis

• Certificate CAS / Certificate of Advanced Studies CAS

• Master MAS / Master of Advanced Studies MAS

• Doctorate / Doktorat

• Secondary technical school / Fachmittelschule

• Basic vocational training (apprenticeship) EFZ / Berufliche Grundbildung (Lehre) EFZ

• Higher technical college HF / Höhere Fachschule HF

• Federal Diploma / Eidg. Diplom

• Vocational Baccalaureate / Berufsmaturität

• MBA / MBA

20

Show profiles

Scenario: User applies profiles without processes.
Given dropdown “Show profiles“,
When select “without processes”, (by default)
Then results show profiles without processes

Scenario: User applies all profiles
Given dropdown “Show profiles“,
When select “All profiles”,
Then results show all profiles

should be added to API by backend developer

Options:

• with processes / Mit Prozessen

• without processes / Ohne Prozesse

21

Market

Scenario: User filters by country.
Given country options exist,
When one is selected,
Then only profiles that are open to work in that market (country).

Select type:

• multiple select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

should be added to API by backend developer

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then: