Add a color scheme test CI for "ISE Nostalgia"

Open
#226 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
powershell
Domain
ci-cd, testing, tooling

Research direction

Start by investigating the SublimeText/UnitTesting functionality mentioned in the issue and how color schemes or syntax scopes are currently tested. Define an automated regression test for the ISE Nostalgia colors using the PowerShell examples shown; done means the test runs in CI and detects unintended scope or color changes.

Written by the indexing model from the issue text.

Description

tooling

I re-built the ISE Nostalgia color scheme by searching for screenshots online. This is the content I managed to come up with as of 2cb109eedb914e3ea898b3c12c598c1d0a823c40.

# Login to your tenant
Add-PowerAppsAccount

$requestBody = @{
    disableSurveyFeedback = $true
}

Set-TenantSettings -RequestBody $requestBody

$psISE.CurrentPowerShellTab.Clear()

function New-OutOfProcRunspace {
    param(
        $ProcessID,
        [Parameter(Position=0,ValueFromPipeline=$True)]
        [string]$Computername=$env:COMPUTERNAME
    )

    $ci = New-Object -TypeName System.Management.Automation -ArgumentList @($ProcessID)
    $tt = [System.Management.Automation.Runspaces.RunspaceFactory]::CreateRunspace($ci)
}

$foo -eq 4

Write-Host "Found $($s.count) ser`vices"

foreach ($server in $Servers) {
    $apps[$ID]
}

I know there's some functionality for SublimeText/UnitTesting to be able to run automated tests as scopes change to regression test the colors, but I haven't really looked into it. If someone wants to figure that out, be my guest.

Dominant language
PowerShell
Stars
335
Forks
80
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SublimeText/PowerShell

All issues in SublimeText/PowerShell

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.