@@ -12,7 +12,8 @@ function Enable-TestNameAsVariablePlugin {
12
12
$state.Plugin += New-PluginObject @PluginParams
13
13
}
14
14
}
15
-
15
+ # Add test name as variable
16
+ # https://github.com/pester/Pester/issues/1611
16
17
BeforeAll {
17
18
# import build variables for test cases
18
19
write-host " Importing Build Variables:"
@@ -64,7 +65,7 @@ Describe 'Migration Test Scenarios' {
64
65
}
65
66
}
66
67
67
- It " Tests for the Scheduled Task already enabled" {
68
+ It " Tests that a previously enabled Scheduled Task is enabled at the end of user migration " {
68
69
# Create a scheduled task
69
70
$action = New-ScheduledTaskAction - Execute " powershell.exe"
70
71
$trigger = New-ScheduledTaskTrigger - AtLogon
@@ -87,7 +88,7 @@ Describe 'Migration Test Scenarios' {
87
88
88
89
89
90
}
90
- It " Tests for the Scheduled Task disabled" {
91
+ It " Tests that a previously disable Scheduled Task is disabled after migration " {
91
92
# Task should be enabled after migration
92
93
# Create a scheduled task
93
94
$action = New-ScheduledTaskAction - Execute " powershell.exe"
@@ -159,7 +160,7 @@ Describe 'Migration Test Scenarios' {
159
160
Remove-Item $logPath
160
161
New-Item $logPath - Force - ItemType File
161
162
}
162
- It " Tests that the tool can recover when the start migration script fails" {
163
+ It " Tests that the tool can recover when the start migration script fails and that scheduled tasks are returned to their previous state " {
163
164
164
165
# This test contains a job which will load the migration user's profile
165
166
# into memory and effectively break the migration process. This test
0 commit comments