René's URL Explorer Experiment

Title: Testing a book's code - by Eric Matthes - Mostly Python

Open Graph Title: Testing a book's code

X Title: Testing a book's code

Description: Maintaining a technical book over a period of years is more challenging than many people realize. Like many software-related projects, automated testing can and should play a role in making sure a book’s code stays up to date. Most people aren’t technical writers though, so the focus of this series is actually on all the little things that come up during the development of a test suite that covers many different kinds of programs. If you’re a technical writer, the benefits of this series are fa

Open Graph Description: Maintaining a technical book over a period of years is more challenging than many people realize. Like many software-related projects, automated testing can and should play a role in making sure a book’s code stays up to date. Most people aren’t technical writers though, so the focus of this series is actually on all the little things that come up during the development of a test suite that covers many different kinds of programs. If you’re a technical writer, the benefits of this series are fa

X Description: Maintaining a technical book over a period of years is more challenging than many people realize. Like many software-related projects, automated testing can and should play a role in making sure a book’s code stays up to date. Most people aren’t technical writers though, so the focus of this series is actually on all the little things that come up during the development of a test suite that covers many different kinds of programs. If you’re a technical writer, the benefits of this series are fa

Opengraph URL: https://www.mostlypython.com/testing-a-books-code-696/

X: @ghost

Generator: Ghost 6.52

direct link

Domain: www.mostlypython.com

{
    "@context": "https://schema.org",
    "@type": "Article",
    "publisher": {
        "@type": "Organization",
        "name": "Mostly Python",
        "url": "https://www.mostlypython.com/",
        "logo": {
            "@type": "ImageObject",
            "url": "https://storage.ghost.io/c/b0/88/b088fa59-ac78-44d9-9662-4c7568d7cb9a/content/images/size/w256h256/2024/02/logo_200px.png",
            "width": 60,
            "height": 60
        }
    },
    "author": {
        "@type": "Person",
        "name": "Eric Matthes",
        "url": "https://www.mostlypython.com/author/eric-matthes/",
        "sameAs": []
    },
    "headline": "Testing a book's code - by Eric Matthes - Mostly Python",
    "url": "https://www.mostlypython.com/testing-a-books-code-696/",
    "datePublished": "2024-01-18T22:15:31.000Z",
    "dateModified": "2024-08-16T20:56:52.000Z",
    "keywords": "Page",
    "description": "Maintaining a technical book over a period of years is more challenging than many people realize. Like many software-related projects, automated testing can and should play a role in making sure a book’s code stays up to date.\n\nMost people aren’t technical writers though, so the focus of this series is actually on all the little things that come up during the development of a test suite that covers many different kinds of programs. If you’re a technical writer, the benefits of this series are fa",
    "mainEntityOfPage": "https://www.mostlypython.com/testing-a-books-code-696/"
}
    

Links:

Viewport: width=device-width, initial-scale=1.0