Skip to content

Documentation Request - adding more "Why do I test" stuff #85

Open

Description

@glennsarti

All,

I was thinking that perhaps I should add a version of my "Beyond Pester 101" and "Beyond Pester 102" talks into this docs repo. However before I start (as it would be a large piece of work) I'd like to make sure it would sit in the vision that the Pester team has for this Docs repo.

Does this sound like something the team would find useful?

Activity

  1. glennsarti commented on Jan 4, 2021

    @glennsarti
    ContributorAuthor

    This would be long-form documentation, taken somewhat from my talks, for this specific project (Pester). Not just linking a transcript

  2. adilio commented on Jan 4, 2021

    @adilio

    I, for one, would find this very useful, yes! 💯

  3. nohwnd commented on Jan 4, 2021

    @nohwnd
    Member

    Yes definitely helpful :)

  4. bravo-kernel commented on Jan 4, 2021

    @bravo-kernel
    Collaborator

    Any suggestions on where those pages should appear (new, separate, etc)?

  5. glennsarti commented on Jan 22, 2021

    @glennsarti
    ContributorAuthor

    Apologies for not getting back sooner....

    @bravo-kernel Right now, I'm not 100% sure. I'm just getting my pester-docs environment setup and then I'll poke around.

  6. glennsarti commented on Jan 22, 2021

    @glennsarti
    ContributorAuthor

    Judging by the current headers...

    image

    It would either sit under "Additional Resources" or perhaps warrant a top level header:

    "What is Software Testing?"
    "Ways to test PowerShell"
    "How do I test PowerShell"
    "Applying Software Testing techniques with Pester"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions