01

Given: email with interview
AND you have already finished the interview 80%

When: click on the button to start the interview in the email

Then: see second thank you page with button Login to the rocken

01

Scenario: Open edit mode

Given: Candidate view page > interview tab

When: click “Edit” button in actual analysis

Then: redirect to edit mode

02

Scenario: One change in edit mode

Given: interview edit mode

When: make 1 change

Then: see the button “Save 1 change“

03

Scenario: Two changes in edit mode

Given: interview edit mode
AND 2 changes

When: click the button “Save 2 changes“

Then: information on the interview tab updated

04

Scenario: Edit actual analysis questions
Given: Profile edit mode > Interview > Actual analysis
When: user views the section
Then: see the following questions:

• "Why are you seeking a new professional challenge?"

• "What tasks and activities fall within your responsibilities?"

• "Where are your professional core competencies within your career path?"

05

Scenario: Update actual analysis answers
Given: Profile edit mode > Interview > Actual analysis
When: user inputs answers for the questions
And: clicks "Save changes"
Then: answers are saved and displayed in the candidate’s profile under the "Interview" tab.

06

Scenario: add hardskills
Given: Profile edit mode > Interview > Actual analysis
When: user views the section with hard skills
Then: see selected skills from candidate

01

Scenario: View interview details
Given: CRM > Talents > Talent Profiles
When: open any candidate by clicking on the name
And: click the button "More info"
And: click on the "Interview" tab
Then: see “Actual Analysis”, “Target Analysis”, and “Personal competencies“

02

Scenario: Switch to edit mode
Given: Candidate view page > Interview tab
AND candidate doesn’t have Rocken Talent account
When: click the "Edit" button
Then: redirect to the edit mode

03

Scenario: Navigate Between Sections Using Anchors
Given I am viewing the Professional tab,
When I click on any of the section anchors (“Actual Analysis”, “Target Analysis”, and “Personal competencies“),
Then I should be smoothly but fast navigated to the relevant section on the page.

04

OOS Scenario: Switch to edit mode
Given: Candidate view page > Interview tab
AND candidate has Rocken Talent account
AND candidate allow editing their profile from the settings
When: click the "Edit" button in CRM
Then: redirect to the edit mode in CRM

05

OOS Scenario: can’t switch to edit mode
Given: Candidate view page > Interview tab
AND candidate has Rocken Talent account
When: don’t see any edit buttons
Then: can’t open edit mode

01

Given: Candidate A has a job OR find it in Rocken talent

When: refer the job to Candidate B
AND submits emails of both candidates

Then: the process is reassigned to candidate B

02

Given: Candidate B has an account

When: system notes that he was referred with name, email, job link to the profile by Candidate A

Then: Candidate A receives the email that candidate B already works with Rocken

03

Given: Candidate B hasn’t an account

When: system creates a profile in CRM with status unfinished
AND system notes: Candidate A (referee), Candidate B (referred), job link

Then: Candidate A receives Email: Thank you, we are happy to get to know about candidate B
AND Email with job to candidate B
AND system notes in the process “referred by Candidate A“

04

Given: candidate B has email with job

When: open vacancy preview page
AND click “Apply“
AND submits his/her information

Then: consultant receives notification about applied referred candidate and pick up the communication
AND process blocked until candidate reaches status Active: error for consultant if he/she trying move on

05

Given: candidate B on finish stage of the process

When: process ROCKED

Then: consultant notification in process: “Note: Referred Candidate by Candidate A“

06

Given: candidate B has email with job

When: open vacancy preview page
AND click NOT interested

Then: Email with CTA to rocken.jobs create a profile

07

Given: Email with CTA to rocken.jobs create a profile

When: apply with creating account

Then: start normal process

08

Given: candidate B has email with job

When: open vacancy preview page
AND don’t click anywhere

Then: send email reminder
AND until apply the status of profile is Unfinished

01

Scenario: Accessing the Forecast Field
Given: Processes list page in CRM
When: Click on the field “Forecast”
Then: Have the ability to change it

02

Scenario: Changing the Forecast by admin
Given: Open editor of the field forecast as admin
When: Change the number
And: Click apply
Then: Forecast is changed

03

Scenario: Changing the Forecast by responsible
Given: Open editor of the field forecast as responsible
When: Change the number
And: Click apply
Then: Forecast is changed

04

Scenario: Changing the Forecast by NOT responsible
Given: process list page as consultant
When: click on forecast where you not responsible
Then: there is not possibility to change it

05

Scenario: Changing the Forecast by business manager
Given: Open editor of the field forecast as business manager of responsible unit
When: Change the number
And: Click apply
Then: Forecast is changed

06

Scenario: Changing the Forecast by business manager but for NOT responsible from your unit
Given: process list page as business manager
When: click on forecast from responsible of other unit
Then: there is not possibility to change it

07

Scenario: Changing the Forecast by division
Given: Open editor of the field forecast as division of responsible group
When: Change the number
And: Click apply
Then: Forecast is changed

08

Scenario: Changing the Forecast by division but for NOT responsible from your group
Given: process list page as division
When: click on forecast from responsible of other division
Then: there is not possibility to change it

09

Scenario: Default Budget Display
Given: Processes list page in CRM
Then: See the budget calculated by default from Desired salary (green numbers)

09a

Scenario: show Job model “Default” forecast
Given: Processes list page in CRM
When: see process with “Default“ Job model vacancy
Then: see green numbers calculated by formula:

18%: desired salary <= 100000
20%: 100000 < desired salary <= 130000
25%: desired salary > 130000

Example 1:
desired Salary 9000
Then Default = 9000*0.18

Example 2:
desired Salary 110000
Then Default = 110000*0.2

Example 3:
desired Salary 150000
Then Default = 150000*0.25

09b

Scenario: show Job model “PaaS” forecast
Given: Processes list page in CRM
When: see process with “PaaS“ Job model vacancy
Then: see green numbers calculated by formula:

18%: desired salary <= 100000
20%: 100000 < desired salary

Example 1:
desired Salary 50000
Then Default = 50000*0.18

Example 2:
desired Salary 120000
Then Default = 120000*0.2

09c

Scenario: show Job model “Executive” forecast
Given: Processes list page in CRM
When: see process with “Executive“ Job model vacancy
Then: see green numbers calculated by formula:

desired salary * 33%

Example:
desired Salary 50000
Then Default = 50000*0.33

10

Scenario: Forecast calculation starts from Interview 2 status
Given the process status has changed to "Interview 2,"
When the candidate reaches this stage,
Then the forecast calculation starts from this moment as it’s more likely that the candidate has a good chance to be rocked (calculating based on desired salary).

11

Scenario: Current salary field must not mandatory
Given the candidate is filling out their details in interview or RT,
When they are prompted for their salary details,
Then the "Current salary" field should still be visible and optional in CRM, Rocken Talent, and Interviews (current salary is not in the formula of forecast).

12

Scenario: Desired salary field remains mandatory
Given a candidate is filling out personal information,
When they are asked to provide their salary expectations,
Then the "Desired salary" field should be mandatory in CRM, Rocken Talent, and Interviews.

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=63570-75948&t=fUEcewBHWR0XzBA4-4

01

Scenario: Filter by Statuses
Given the processes list page,
When selecting from the available status filters,
Then the list should display only processes that match the selected status.

02

Scenario: search field location
Given I am on the Process List page,
When I view the page,
Then the search field should be placed on the top-right side of the page.

https://cheitgroup.atlassian.net/wiki/spaces/RD/pages/1027670215/Story+1.6.3.7.+CRM.+Process.+Search+field?force_transition=26fa9d9b-a588-4fe8-b360-f828a0fa4642

03

Scenario: Opening the Filters panel
Given I am on the processes 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. Sales/Account / Sales/Account

2. Management consultant / Management consultant

3. Responsible / Verantwortlich

4. Recruiter / Recruiter

5. Process creation date / Process Erstellungsdatum

6. Last Update / Letzte Aktualisierung

7. Market / Markt

8. Candidate / Kandidat

9. Company / Unternehmen

10. Interview date / Interview Zeit

11. Candidate rejected: reason / Kandidat abgelehnt: Grund

12. Company rejected: reason / Unternehmen abgelehnt: Grund

04

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#/Process/get_api_v1_processes

01

Sales/Account

Scenario: User applies a Sales/Account filter.
Given Sales/Account field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

02

Management consultant

Scenario: User applies a Management consultant filter.
Given Management consultant field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

03

Responsible

Scenario: User applies a Consultant filter.
Given Consultant field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

04

Recruiter

Scenario: User applies a Recruiter filter.
Given Recruiter field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

05

Process creation date

Scenario: User filters by process creation date.
Given the user inputs "From" and "To" values for process creation date,
When valid,
Then results show processes in the range.

should be added to API by backend developer

06

Last Update

Scenario: User filters by Last update.
Given the user inputs "From" and "To" values,
When valid,
Then results show processes in the range.

updated_from

updated_to

07

Market

Scenario: User filters by market.
Given market options exist,
When one is selected,
Then only processes for that market (country) should be shown.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

should be added to API by backend developer

08

Candidate

Scenario: User applies a Candidate filter.
Given Candidate field,
When select talent profile,
Then results show processes with this talent profiles.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

09

Company

Scenario: User applies a Company filter.
Given the user enters a Company name,
When the name exists,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags

should be added to API by backend developer

10

Interview date

Scenario: User filters by creation date.
Given the user inputs "From" and "To" values for process creation date,
When valid,
Then results show processes in the range.

should be added to API by backend developer

11

Candidate rejected: reason

Scenario: User applies the reason of candidate rejected
Given user interact with dropdown rejection reasons,
When select one of rejection reason,
Then filter automatically applied.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

candidate_rejected[]

Available values :

• working location / Arbeitsort

• qualifications / Qualifikationen

• company profile / Firmenprofil

• already applied / bereits beworben

• custom reason / individueller Grund

12

Company rejected: reason

Scenario: User applies the reason of company rejected
Given user interact with dropdown rejection reasons,
When select one of rejection reason,
Then filter automatically applied.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

company_rejected[]

Available values :

• experience / Erfahrung

• education / Ausbildung

• industry knowledge / Branchenkenntnisse

• salary / Gehalt

• references / Referenzen

• skills / Fähigkeiten

• overqualification / Überqualifizierung

• underqualification / Unterqualifizierung

• custom reason / individueller Grund

01

Scenario: Reassign activities

Given: user list

When: click edit on the user
AND scroll down
AND select another CRM User (display only Active status users)
AND click SAVE

Then: all activities is changed to another CRM user depending on their role:

• applications

• profiles

• processes

• publications

• vacancies

• companies

• orders

DE:

“Von einem Kollege(n) übernommen:” [selector of all users in the system]

EN:

“Covered by colleague(s):” [selector of all users in the system]