ver 1.0 htmml files problem

[akikujanenc2]

html files wont open. Bug or I just missing something? Maester 0.3.0 was working fine. First time trying version 1.0.
It creates file and file size indicates that there is data, just wont see it.

[stfnbrndg]

I believe I'm having this same issue. The previous version of Maester outputted HTML that opened just fine on my Mac. Maester 1.0 produces HTML files (alongside the .json and Markdown files) but it's just displaying as blank in the browser (tried Safari + Firefox).

[AkiKujanen]

any news or ideas what might be causing this?

[lukasgd1913]

I was able to recreate the behavior. I don't know whether this will also work as a workaround for you.

The report was ok with a clean installation.
When I used the example from the following link I got the error:
https://maester.dev/docs/ca-what-if#example-2-test-if-non-admin-users-are-blocked-from-accessing-the-azure-portal

It works for me to define more than one “tag”.
Like:
Describe "ContosoEntraConfig" -Tag "CA", "Contoso" {

Link to formatting guide:
https://maester.dev/docs/writing-tests/formatting-test-results#a-custom-maester-test-to-check-conditional-access-policies-standards

@stfnbrndg @AkiKujanen @akikujanenc2 - maybe a workaround for you too.

[AkiKujanen]

I uninstalled maester module (all versions) and made clean installation of Maester module 1.0.0, but it didnt help.
I do have some custom queries also and those allready have more than one tag.
I did remove my custom queries but that didnt help.

[ntatschner]

Same HTML file error here, props.Item.Tag.map is not a function seems like the variable a4 in each function using it.
Specifically function ResultInfoDialog

[Lil-Mihend]

running into the same issue. Appears to be an issue with the props.Item.Tag.map logic.

[anderskortsen]

I am too running into the same issue on v1.0. No issue prior to update (had v0.3 before as well). I tried to remove/delete my custom tests (which had two tags), but it did not solve the issue.
From the dev tools I get shown the following errors:

[scs-ash]

I encountered the same problem. After installing Maester v1.0.0 and updating the tests, I discovered that Maester was still defaulting to v0.3.0. Once I removed the older version, Maester ran as v1.0.0 but couldn’t load the test results. It turned out the tests were still from v0.3.0, so updating them again finally resolved the issue.

The steps to fix for me were:

1. Update Maester to v1.0.0 with Update-Module Maester
2. Remove v0.3.0 with Get-Module 'Maester' | where {([string]($_.Version)).StartsWith('0.3.0')} | Remove-Module
3. Update the tests with Update-MaesterTests

[anderskortsen]

I encountered the same problem. After installing Maester v1.0.0 and updating the tests, I discovered that Maester was still defaulting to v0.3.0. Once I removed the older version, Maester ran as v1.0.0 but couldn’t load the test results. It turned out the tests were still from v0.3.0, so updating them again finally resolved the issue.

The steps to fix for me were:

1. Update Maester to v1.0.0 with Update-Module Maester
2. Remove v0.3.0 with Get-Module 'Maester' | where {([string]($_.Version)).StartsWith('0.3.0')} | Remove-Module
3. Update the tests with Update-MaesterTests

After cleaning up the old v0.3.0 and updating the tests again it solved the issue for me as well! Brilliant. Thanks for sharing the solution!

[erik-wo]

I'm now having the same problem with blank html report page. Any other solutions to this problem? Above solution didn't work for me.

[lupintoro]

Hi everyone,

I encounter this problem only if I'm running the tests outside the folder "maester-tests". Inside the folder everything is ok.

But when I run the tests inside the folder I have a total of approx. 200 tests , whereas outside the folder I get 2000 tests. Can someone explain me this difference?

[stfnbrndg]

I encountered the same problem. After installing Maester v1.0.0 and updating the tests, I discovered that Maester was still defaulting to v0.3.0. Once I removed the older version, Maester ran as v1.0.0 but couldn’t load the test results. It turned out the tests were still from v0.3.0, so updating them again finally resolved the issue.

The steps to fix for me were:

1. Update Maester to v1.0.0 with Update-Module Maester
2. Remove v0.3.0 with Get-Module 'Maester' | where {([string]($_.Version)).StartsWith('0.3.0')} | Remove-Module
3. Update the tests with Update-MaesterTests

This worked for me, thanks very much!