🧪 Add a seeded verified employee profile

[JoshBeveridge]

🕵️ Details

Looking to test @mnigh's PR #12433 but struggled to access employee tools post-build because of verification limitations (and my own DB limitations).

🙋‍♀️ Proposed Solution

Add an [email protected] user with:

• a pre-verified work email
• employee profile
• one current government work experience

Remove any employee-specific stuff from the default [email protected] user

✅ Acceptance Criteria

• Seeder creates [email protected] user with:
  • a pre-verified work email
  • employee profile
  • one current government work experience
• [email protected] user does not get withEmployeeProfile when seeded, does not have verified work email, does not have any gov work experiences

[mnigh]

@esizer would it make sense to modify the function withEmployeeProfile so that it verifies user there or create a new function called something like withVerifiedEmails that does the work there? That way, we wouldn't need to create a new seeder user, we could use [email protected]. Thoughts?

gc-digital-talent/api/database/factories/UserFactory.php

Lines 216 to 251 in 3910f9c

	public function withEmployeeProfile()
	{
	return $this->afterCreating(function (User $user) {
	$community = Community::inRandomOrder()->first();
	if (is_null($community)) {
	$community = Community::factory()->withWorkStreams()->create();
	}
	$classification = Classification::inRandomOrder()->first();
	if (is_null($classification)) {
	$classification = Classification::factory()->create();
	}
	$workStream = $this->faker->randomElement($community->workStreams);
	$departments = Department::inRandomOrder()->limit($this->faker->numberBetween(1, 3))->get();
	$user->employeeProfile->dreamRoleDepartments()->sync($departments);
	$user->employeeProfile()->update([
	'career_planning_organization_type_interest' => $this->faker->randomElements(array_column(OrganizationTypeInterest::cases(), 'name'), null),
	'career_planning_move_interest' => $this->faker->randomElements(array_column(MoveInterest::cases(), 'name'), null),
	'career_planning_mentorship_status' => $this->faker->optional(weight: 70)->randomElements(array_column(Mentorship::cases(), 'name'), null),
	'career_planning_mentorship_interest' => $this->faker->optional(weight: 70)->randomElements(array_column(Mentorship::cases(), 'name'), null),
	'career_planning_exec_interest' => $this->faker->boolean(),
	'career_planning_exec_coaching_status' => $this->faker->optional(weight: 80)->randomElements(array_column(ExecCoaching::cases(), 'name'), null),
	'career_planning_exec_coaching_interest' => $this->faker->optional(weight: 80)->randomElements(array_column(ExecCoaching::cases(), 'name'), null),
	'career_planning_about_you' => $this->faker->paragraph(),
	'career_planning_career_goals' => $this->faker->paragraph(),
	'career_planning_learning_goals' => $this->faker->paragraph(),
	'career_planning_work_style' => $this->faker->paragraph(),
	'dream_role_title' => $this->faker->words(3, true),
	'dream_role_additional_information' => $this->faker->paragraph(),
	'dream_role_community_id' => $community->id,
	'dream_role_classification_id' => $classification->id,
	'dream_role_work_stream_id' => $workStream?->id,
	]);
	});
	}

gc-digital-talent/api/database/seeders/UserTestSeeder.php

Lines 91 to 101 in 3910f9c

	User::factory()
	->asApplicant()
	->withSkillsAndExperiences()
	->withEmployeeProfile()
	->withCommunityInterests([$testCommunityId])
	->create([
	'first_name' => 'Gul',
	'last_name' => 'Fields',
	'email' => '[email protected]',
	'sub' => '[email protected]',
	]);

[esizer]

@esizer would it make sense to modify the function withEmployeeProfile so that it verifies user there or create a new function called something like withVerifiedEmails that does the work there? That way, we wouldn't need to create a new seeder user, we could use [email protected]. Thoughts?

Modifying withEmployee profile makes sense as long as we document it. Since uswers can't even add an employee profile without being verified makes sense to me 👍