Scribd Logo
Upload

Welcome to Scribd!

  • Js Testing

    Uploaded by

    Brian Mwanzia
    8 views1 page
    This document discusses different types of JavaScript testing including unit testing, acceptance testing, integration testing, mocks, stubs, and spies. It recommends unit testing small pieces of code, complex user flows, and integration points. Mocks replace imported classes with custom implementations while stubs replace specific parts of code. Spies verify function calls without altering outcomes and can be used to spy on library methods. The document also suggests testing authentication, code coverage, and asking if code breaking would negatively impact the application.

    Original Description:

    Notes from Vue js on javascript testing

    Original Title

    js testing

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses different types of JavaScript testing including unit testing, acceptance testing, integration testing, mocks, stubs, and spies. It recommends unit testing small pieces of code, complex user flows, and integration points. Mocks replace imported classes with custom implementations while stubs replace specific parts of code. Spies verify function calls without altering outcomes and can be used to spy on library methods. The document also suggests testing authentication, code coverage, and asking if code breaking would negatively impact the application.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    8 views1 page

    Js Testing

    Uploaded by

    Brian Mwanzia
    This document discusses different types of JavaScript testing including unit testing, acceptance testing, integration testing, mocks, stubs, and spies. It recommends unit testing small pieces of code, complex user flows, and integration points. Mocks replace imported classes with custom implementations while stubs replace specific parts of code. Spies verify function calls without altering outcomes and can be used to spy on library methods. The document also suggests testing authentication, code coverage, and asking if code breaking would negatively impact the application.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    JavaScript Testing

    17 August 2023 09:36

    Why test?
    - Code confidence
    - Documentation
    - Easy refactoring
    - Better development
    - Team work

    See files in javascript-testing-fundamentals-master file

    What to test?
    - Asking: would it be bad for the app if this code breaks?
    Constructors need not be tested individually, they're called in
    every other test case.
    Test authentication: is the user an admin?
    How much code is covered by a test?
    Test Coverage - how much code is covered by a test?

    Types - AIU
    Unit testing - small pieces of code, complex user flows, in
    betweens.
    Acceptance tests (end-to-end tests) - complex flows.
    Integration/functional tests - in between stuff
    - Verify the code is working

    Mocks/mocking
    Replacing imported Permissions class with custom mock
    implementation. Though the example is done on the same file,
    in the real world it is structured in different files.

    Stubs
    While mocks replace what was there before, stubs replace a
    specific piece of what was there before.

    Spies
    Verifying a function without altering the outcome, in a less
    extensive format, we use spying on libraries to assign methods
    in order to spy the associated object.

    You might also like