sp-dev-fx-webparts/samples/react-ioc-tests
Hugo Bernier 68f7f67761 Changed from updated to modificationDateTime 2021-05-02 15:39:42 -04:00
..
assets Changed from updated to modificationDateTime 2021-05-02 15:39:42 -04:00
config added react-ioc-tests sample web part (#815) 2019-04-08 12:34:40 +03:00
pipelines Updating react-ioc-tests sample (#1141) 2020-03-09 19:58:27 +02:00
src Updating react-ioc-tests sample (#1141) 2020-03-09 19:58:27 +02:00
vscode added react-ioc-tests sample web part (#815) 2019-04-08 12:34:40 +03:00
.editorconfig added react-ioc-tests sample web part (#815) 2019-04-08 12:34:40 +03:00
.gitignore Updating react-ioc-tests sample (#1141) 2020-03-09 19:58:27 +02:00
.yo-rc.json added react-ioc-tests sample web part (#815) 2019-04-08 12:34:40 +03:00
README.md Changed master to main 2021-05-02 15:04:59 -04:00
gulpfile.js added react-ioc-tests sample web part (#815) 2019-04-08 12:34:40 +03:00
package-lock.json Updating react-ioc-tests sample (#1141) 2020-03-09 19:58:27 +02:00
package.json Updating react-ioc-tests sample (#1141) 2020-03-09 19:58:27 +02:00
tsconfig.json Updating react-ioc-tests sample (#1141) 2020-03-09 19:58:27 +02:00
tslint.json added react-ioc-tests sample web part (#815) 2019-04-08 12:34:40 +03:00

README.md

React Inversion Of Control with Unit Tests using Jest and Enzyme

Summary

This web part is provided as an example of implementing an IoC (Inversion of Control) pattern, primarily to enable unit testing, in the context of a SharePoint Framework web part.

Following this pattern greatly improves the modularity, maintainability, and testability of the code.

The example includes 100% test coverage, using Jest and Enzyme, of .ts and .tsx files, excluding *WebPart.ts files. A dependency resolver class specific to a web part class is used to map web part properties to component properties and create any dependent services/providers.

This pattern is implemented to separate testable logic from the untestable *WebPart.ts file and hence ensure that all relevant web part logic is tested. To this end, a Service class is paired with a ServiceExecutor class which should extract the actual service requests from other service logic ensuring that the Service class remains fully testable. *Executor classes are excluded from test coverage as they cannot be unit tested by design - as they are points integration.

Included in the coverage is a cache and logger class, along with a service class that fetches data asynchronously using @pnp/sp 2.x

The example also includes a pipeline definition .yaml file for Azure DevOps CI build pipeline (/pipelines/) which includes the build, running tests, and posting the test coverage results.

Sample SPFx Web Part implementing IoC pattern

Used SharePoint Framework Version

drop

Applies to

Solution

Solution Author(s)
react-ioc-tests Paul Ryan

Version history

Version Date Comments
1.0 March 20, 2019 Initial release

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.


Minimal Path to Awesome

  • Clone this repository
  • in the command line run:
    • npm install
    • npm bundle
    • npm test
    • gulp serve

Features

This web part is provided as an example of implementing an IoC (Inversion of Control) pattern in the context of a SharePoint Framework web part for maximising testability. This Web Part illustrates the following concepts on top of the SharePoint Framework:

  • Inversion of Control pattern
  • Unit testing with Jest and Enzyme
  • Azure DevOps CI Build Pipeline yaml definition file, includes running tests and checking code coverage

References

https://github.com/pnp/sp-dev-fx-webparts/tree/main/samples/react-jest-testing

https://blog.velingeorgiev.com/unit-test-your-sharepoint-framework-solution-with-jest

https://www.eliostruyf.com/sharepoint-framework-unit-tests-with-jest/

https://github.com/estruyf/spfx-testing-jest