Add RunPageScriptingTests parameter and implementation to Run-AlPipeline #4052
Conversation
…ine microsoft#2001 * Pass the parameters as a hashtable to RunPageScriptingTests function so that they can be adjusted later in a non-breaking manner. * do a depper check on bcAuthContext to differ saas envionments from other. * do not check if the container was lef created before running page scripting tests.
ChrisBlankDe
changed the title
| Write-GroupEnd | ||
| } | ||
|
|
||
| if ($createContainer -and !$doNotRunPageScriptingTests -and $pageScriptingTests -and $pageScriptingTestResultsFolder -and $pageScriptingTestResultsFile) { |
There was a problem hiding this comment.
Why would you not check that a container is created when restoring the database in a container?
Else, I assume this could fail with CompilerFolder running
There was a problem hiding this comment.
Just because you use CompilerFolder doesn't necessarily mean you don't have a container.
That's only the case if you set doNotPublishApps at the same time. But if you set this, doNotRunPageScriptingTests is automatically set to true. That would make it OK again, right?
AppHandling/Run-AlPipeline.ps1
Outdated
| $artifactUrl = "" | ||
| $filesOnly = $false | ||
| if ($bcAuthContext) { | ||
| $IsBcSaaSInfrastructure = $bcAuthContext -and $bcAuthContext -is [Hashtable] -and $bcAuthContext.ContainsKey('scopes') -and $bcAuthContext.scopes -in @('https://api.businesscentral.dynamics.com/', 'https://projectmadeira.com/') |
There was a problem hiding this comment.
I think it needs to be projectmadeira.
There was a problem hiding this comment.
I wasn't entirely sure while development because the context goes to dynamics.com by default.
I have now synchronized it with the logic in Run-TestsInNavContainer.ps1.
2 participants
fixes AL-Go#2001