[All Hosts] (testing) How to use the Office mocking library #3079

Rick-Kirkham · 2021-11-15T01:45:53Z

Fixes 1611
Fixes 584

Note to reviewers: More detailed examples in the last section of the article will be part of a Phase 2 PR in a future quarter.

NOTE TO REVIEWERS: There will be cross-links between this article and the Readme of the repo for Office-Addin-Mock. So, the content of the two has to be coordinated and made consistent. There's no practical way to do that until after this article is close to finalized. Then there will be a separate PR for the the Readme. Nothing will be published until both documents are done and mutually consistent.

opbld33 · 2021-11-15T01:46:43Z

Docs Build status updates of commit 8e25720:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/testing/unit-testing.md	⚠️Warning	View	Details
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

docs/testing/unit-testing.md

Line 14, Column 79: [Warning: file-not-found - See documentation] Invalid file link: '../develop/understanding-the-javascript-api-for-office'.
Line 14, Column 231: [Warning: file-not-found - See documentation] Invalid file link: '../develop/application-specific-api-model'.
Line 14, Column 292: [Warning: file-not-found - See documentation] Invalid file link: '../develop/application-specific-api-model'.
Line 232, Column 52: [Warning: file-not-found - See documentation] Invalid file link: 's/javascript/api/excel'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld32 · 2021-11-15T01:49:28Z

Docs Build status updates of commit 35dbde6:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/testing/unit-testing.md	⚠️Warning	View	Details
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

docs/testing/unit-testing.md

Line 14, Column 79: [Warning: file-not-found - See documentation] Invalid file link: '../develop/understanding-the-javascript-api-for-office'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld34 · 2021-11-15T01:51:08Z

Docs Build status updates of commit 2ca7bb9:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

docs/testing/unit-testing.md

igor-ribeiiro · 2021-11-15T18:12:58Z

docs/testing/unit-testing.md

+    > [!NOTE]
+    > Full reference documentation for the `OfficeMockObject` type is at [Office-Addin-Mock](https://github.com/OfficeDev/Office-Addin-Scripts/tree/master/packages/office-addin-mock).
+
+1. In the syntax of your test framework, add a test of the function, but use the `OfficeMockObject` object in place of the object that it mocks, in this case the `ClientRequestContext` object. The following continues the example in Jest. This example test assumes that the add-in function that is being tested is called `getSelectedRangeAddress`, that it takes a `ClientRequestContext` object as a parameter, and that it is intended to return the address of the currently selected range. The full example is at [Mocking a ClientRequestContext object](#mocking-a-clientrequestcontext-object).


"being tested is called" -> "being tested called"

I think it's right as is.

I agree with millerds. I think adding the "is" makes the whole sentence ungrammatical.

docs/testing/unit-testing.md

AlexJerabek

Thanks @Rick-Kirkham! This is looking good. It's exciting to finally see this feature come to life.

I left some IA suggestions. I can do a more thorough review afterwards.

docs/testing/unit-testing.md

AlexJerabek · 2021-11-15T18:35:39Z

docs/testing/unit-testing.md

+   npm test
+   ```
+
+## Examples


What do you think about moving these example setup steps above the "Basic usage" section? I think that preempts questions like "what test file do I add the require statement to". It also gets people to a working version of unit tests faster.

What do you think about moving these example setup steps above the "Basic usage" section? I think that preempts questions like "what test file do I add the require statement to". It also gets people to a working version of unit tests faster.

I'm not keen on separating the example setup from the Examples section. Understanding what a test file is is part of the prerequisites. To address your concerns, I've added info to the Prerequisites section and the first step of the Basic usage section.

docs/testing/unit-testing.md

AlexJerabek · 2021-11-15T18:44:44Z

docs/testing/unit-testing.md

+- The Office JavaScript APIs must initialize in a webview control in the context of an Office application (Excel, Word, etc.), so they cannot be loaded in the process in which unit tests run on your development computer.
+- Some unit testing frameworks require that mock objects emulate all the members of the object type that is being mocked, which isn't feasible for the Office JavaScript APIs because some object types have over a hundred members.
+- Unit testing frameworks are stateless, which makes it difficult to test the [application-specific APIs](../develop/understanding-the-javascript-api-for-office.md#api-models) in the Office JavaScript APIs, because they have methods [load()](../develop/application-specific-api-model.md#load) and [sync()](../develop/application-specific-api-model.md#sync) that must be called in a particular order relative to other functions and to each other.
+
+To solve these problems, we have created a library to simplify the creation of mock Office objects in unit tests: [Office-Addin-Mock](https://github.com/OfficeDev/Office-Addin-Scripts/tree/master/packages/office-addin-mock).
+
+The library doesn't depend on the Office JavaScript APIs and it can be used with any JavaScript unit testing framework, including the following among others:


I like this explanation of why unit testing the Office JS library is hard. Is there a way to frame this list as a set of solutions Office-Addin-Mock provides? So, instead of saying load/sync is hard to test, we say that the mock library makes that easy to test? I also think that'll align well with your prerequisite that readers already be familiar with unit testing.

Rewrote the first and 3rd bullets. Consulting with SMEs about the middle one.

Deleted middle bullet. What it referred to is not really anything to do with the Office-Addin-Mock.

AlexJerabek · 2021-11-15T19:02:09Z

docs/testing/unit-testing.md

+   - The mock object will mimic crucial error behavior of the `ClientRequestContext` object. For example, if the Office API you are testing tries to read a property without first loading the property and calling `sync()`, then the test will fail with an error similar to what would be thrown in production runtime: "Error, property not loaded".
+
+   ```javascript
+   const contextMock = new OfficeMockObject.OfficeMockObject(mockData);


I didn't see this creation pattern in the linked docs. I saw const wordMock = new officeAddinMock.OfficeMockObject(WordMockData); and const officeMock = new OfficeMockObject(PowerPointMockData);. This confused me. Should that first example have a capital "O"?

My bad. I forgot to add the following to the PR description. I'll add it now.

NOTE TO REVIEWERS: There will be cross-links between this article and the Readme of the repo for Office-Addin-Mock. So, the content of the two has to be coordinated and made consistent. There's no practical way to do that until after this article is close to finalized. Then there will be a separate PR for the the Readme. Nothing will be published until both documents are done and mutually consistent.

docs/testing/unit-testing.md

AlexJerabek · 2021-11-15T19:10:17Z

docs/testing/unit-testing.md

+module.exports = myExcelAddinFeature;
+```
+
+The test file, named `my-excel-add-in-feature.test.js` is in a subfolder, relative to the location of the add-in code file. The following shows the contents of the file. Note that the top level property is `workbook`, so the object that is being mocked is the parent of an `Excel.workbook`: a `ClientRequestContext` object.


I believe "an Excel.workbook" should either be "an Excel.Workbook" (if we're referring to the object type) or "Excel.workbook" (if we're referring to the host-object property).

docs/testing/unit-testing.md

millerds · 2021-11-15T19:21:41Z

docs/testing/unit-testing.md

+    > [!NOTE]
+    > Full reference documentation for the `OfficeMockObject` type is at [Office-Addin-Mock](https://github.com/OfficeDev/Office-Addin-Scripts/tree/master/packages/office-addin-mock).
+
+1. In the syntax of your test framework, add a test of the function, but use the `OfficeMockObject` object in place of the object that it mocks, in this case the `ClientRequestContext` object. The following continues the example in Jest. This example test assumes that the add-in function that is being tested is called `getSelectedRangeAddress`, that it takes a `ClientRequestContext` object as a parameter, and that it is intended to return the address of the currently selected range. The full example is at [Mocking a ClientRequestContext object](#mocking-a-clientrequestcontext-object).


I think it's right as is.

opbld34 · 2021-11-15T21:23:11Z

Docs Build status updates of commit ac3c81b:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld31 · 2021-11-15T21:27:40Z

Docs Build status updates of commit ed20631:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld31 · 2021-11-15T23:49:27Z

Docs Build status updates of commit 123f4dc:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

AlexJerabek

Thanks @Rick-Kirkham! I added some comments and suggestions for your consideration.

docs/testing/unit-testing.md

AlexJerabek · 2021-11-16T19:21:43Z

docs/testing/unit-testing.md

+Unit tests check your add-in's functionality without requiring network or service connections, including connections to the Office application. Unit testing server-side code, and client-side code that does *not* call the [Office JavaScript APIs](../develop/understanding-the-javascript-api-for-office.md), is the same in Office Add-ins as it is in any web application, so it requires no special documentation. But client-side code that calls the Office JavaScript APIs is challenging to test. To solve these problems, we have created a library to simplify the creation of mock Office objects in unit tests: [Office-Addin-Mock](https://www.npmjs.com/package/office-addin-mock). The library makes testing easier in the following ways:
+
+- The Office JavaScript APIs must initialize in a webview control in the context of an Office application (Excel, Word, etc.), so they cannot be loaded in the process in which unit tests run on your development computer. The Office-Addin-Mock library can be imported into your test files, which enables the mocking of Office JavaScript APIs inside the node.js process in which the tests run.
+- Unit testing frameworks are stateless, which makes it difficult to test the [application-specific APIs](../develop/understanding-the-javascript-api-for-office.md#api-models) in the Office JavaScript APIs, because they have methods [load](../develop/application-specific-api-model.md#load) and [sync](../develop/application-specific-api-model.md#sync) that must be called in a particular order relative to other functions and to each other. The mock objects that you create with the Office-Addin-Mock library automatically have mock implementations of `load` and `sync`.


Suggestion to reframe the challenge in terms of Office JS, instead of the unit testing "ideals".

Suggested change

- Unit testing frameworks are stateless, which makes it difficult to test the [application-specific APIs](../develop/understanding-the-javascript-api-for-office.md#api-models) in the Office JavaScript APIs, because they have methods [load](../develop/application-specific-api-model.md#load) and [sync](../develop/application-specific-api-model.md#sync) that must be called in a particular order relative to other functions and to each other. The mock objects that you create with the Office-Addin-Mock library automatically have mock implementations of `load` and `sync`.

- The [application-specific APIs](../develop/understanding-the-javascript-api-for-office.md#api-models) in the Office JavaScript APIs are difficult to test because the [load](../develop/application-specific-api-model.md#load) and [sync](../develop/application-specific-api-model.md#sync) methods create complex states. The mock objects that you create with the Office-Addin-Mock library automatically have mock implementations of `load` and `sync`. This lets you control the state of the unit test environment.

I'm researching this with the SMEs.

After consulting with SMEs, I've rewritten this bullet to clarify what it is saying.

docs/testing/unit-testing.md

AlexJerabek · 2021-11-16T20:01:10Z

docs/testing/unit-testing.md

+In some scenarios, efficient testing requires that mock objects be created or modified at runtime; that is, while the tests are running. The following are examples:
+
+- The function that is being tested behaves differently when called a second time, from how it behaves when first called. You need to first test the function with one mock object, then change this mock object and test the function again with the changed mock object.
+- You need to test a function against multiple arguments quickly. For example, you need to test a function with a mock object that has a color property and then test the function again with a mock object that has a text property, but is otherwise identical to the original mock object.


I'm unclear why "quickly" is a factor in the tests. It seems like the scenario is just editing the same mock object after construction.

docs/testing/unit-testing.md

AlexJerabek · 2021-11-16T20:03:34Z

docs/testing/unit-testing.md

+    rangeMock.setMock("address", "G6:K9");
+    ```
+
+- `OfficeMockObject.addMockFunction` adds a mock function to a `OfficeMockObject` object. If the function parameter isn't used, an empty function is created. The following is an example:


It's a little confusing to read about the empty parameter case before seeing an example that doesn't use it. Maybe pull that line out as a note that follows the sample code?

AlexJerabek · 2021-11-16T20:05:13Z

docs/testing/unit-testing.md

+- `OfficeMockObject.addMock` adds a new `OfficeMockObject` object as a property to an existing one and gives it a name. It would have the minimum members that all `OfficeMockObject` have, such as `load` and `sync`. Additional members can be added with the `setMock` and `addMockFunction` methods. The following is an example:
+
+    ```javascript
+    workbookMock.addMock("range");


Is this adding a mock property called "range" to the mock workbook? I'm confused because this doesn't map to my mental picture of the Excel object model.

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

opbld30 · 2021-11-16T21:35:10Z

Docs Build status updates of commit 043f3ab:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld30 · 2021-11-16T21:35:46Z

Docs Build status updates of commit 043f3ab:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

opbld31 · 2021-11-16T21:36:52Z

Docs Build status updates of commit c1b5e3a:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

opbld30 · 2021-11-16T21:37:45Z

Docs Build status updates of commit 2594783:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

opbld32 · 2021-11-16T21:38:29Z

Docs Build status updates of commit f80b9c8:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

opbld33 · 2021-11-16T21:39:53Z

Docs Build status updates of commit 0517d94:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld31 · 2021-11-16T21:40:39Z

Docs Build status updates of commit 3d731cd:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

opbld33 · 2021-11-16T21:42:38Z

Docs Build status updates of commit 8fb72e5:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld30 · 2021-11-16T22:08:23Z

Docs Build status updates of commit b32b0c6:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld34 · 2021-11-17T18:28:06Z

Docs Build status updates of commit 26b52aa:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld30 · 2021-11-18T00:42:16Z

Docs Build status updates of commit 7c8519b:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

AlexJerabek

Looks good! I left a couple minor comments, but I don't need to re-review unless there's a drastic change.

docs/testing/unit-testing.md

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

opbld30 · 2021-11-18T01:00:13Z

Docs Build status updates of commit d420eb4:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld32 · 2021-11-19T00:17:09Z

Docs Build status updates of commit c5bf511:

✅ Validation status: passed

File	Status	Preview URL
docs/testing/test-debug-office-add-ins.md	✅Succeeded	View
docs/testing/unit-testing.md	✅Succeeded	View
docs/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

[All Hosts] (testing) How to use the Office mocking library (#3079)

Rick-Kirkham added 9 commits November 13, 2021 15:41

[All Hosts] (testing) new unit testing article

d3e50d7

added Common API test and dynamic mock creation

54c54f7

remove 'stub' terminology

b2d3701

small fixes

8761929

fix note indentation

1243b2b

fix note indentation

dbe7c26

remove misleading note

24ccd29

add Outlook example

db2dde4

add prerequisites

8e25720

fix build errors

35dbde6

fix build errors

2ca7bb9

Rick-Kirkham requested review from lindalu-MSFT and AlexJerabek November 15, 2021 01:53

igor-ribeiiro suggested changes Nov 15, 2021

View reviewed changes

AlexJerabek requested changes Nov 15, 2021

View reviewed changes

millerds reviewed Nov 15, 2021

View reviewed changes

review changes

ac3c81b

typo

ed20631

removing misleading item from the library's virtues

123f4dc

Rick-Kirkham requested review from AlexJerabek and igor-ribeiiro November 15, 2021 23:48

AlexJerabek reviewed Nov 16, 2021

View reviewed changes

Rick-Kirkham and others added 2 commits November 16, 2021 13:23

Update docs/testing/unit-testing.md

3e71e0d

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Update docs/testing/unit-testing.md

918233b

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Rick-Kirkham and others added 2 commits November 16, 2021 13:35

Update docs/testing/unit-testing.md

c1b5e3a

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Update docs/testing/unit-testing.md

2594783

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Update docs/testing/unit-testing.md

f80b9c8

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Update docs/testing/unit-testing.md

1df0f6b

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Rick-Kirkham and others added 2 commits November 16, 2021 13:38

Update docs/testing/unit-testing.md

0517d94

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Update docs/testing/unit-testing.md

3d731cd

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

Update docs/testing/unit-testing.md

8fb72e5

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

review changes

b32b0c6

rewrite virtue bullet to clarify

26b52aa

Rick-Kirkham requested a review from AlexJerabek November 17, 2021 18:31

typo

7c8519b

AlexJerabek approved these changes Nov 18, 2021

View reviewed changes

Apply suggestions from code review

d420eb4

Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com>

links to new repo readme

c5bf511

Rick-Kirkham merged commit 5473085 into master Nov 19, 2021

Rick-Kirkham added a commit that referenced this pull request Nov 19, 2021

Merge pull request #3096 from OfficeDev/master

67b70f5

[All Hosts] (testing) How to use the Office mocking library (#3079)

Rick-Kirkham deleted the mocking-library branch January 21, 2022 00:08

[All Hosts] (testing) How to use the Office mocking library #3079

[All Hosts] (testing) How to use the Office mocking library #3079

Conversation

Rick-Kirkham commented Nov 15, 2021 • edited

opbld33 commented Nov 15, 2021

⚠️ Validation status: warnings

opbld32 commented Nov 15, 2021

⚠️ Validation status: warnings

opbld34 commented Nov 15, 2021

✅ Validation status: passed

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AlexJerabek left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

opbld34 commented Nov 15, 2021

✅ Validation status: passed

opbld31 commented Nov 15, 2021

✅ Validation status: passed

opbld31 commented Nov 15, 2021

✅ Validation status: passed

AlexJerabek left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

opbld30 commented Nov 16, 2021

✅ Validation status: passed

opbld30 commented Nov 16, 2021

✅ Validation status: passed

opbld31 commented Nov 16, 2021

✅ Validation status: passed

opbld30 commented Nov 16, 2021

✅ Validation status: passed

opbld32 commented Nov 16, 2021

✅ Validation status: passed

opbld33 commented Nov 16, 2021

✅ Validation status: passed

opbld31 commented Nov 16, 2021

✅ Validation status: passed

opbld33 commented Nov 16, 2021

✅ Validation status: passed

opbld30 commented Nov 16, 2021

✅ Validation status: passed

opbld34 commented Nov 17, 2021

✅ Validation status: passed

opbld30 commented Nov 18, 2021

✅ Validation status: passed

AlexJerabek left a comment

Choose a reason for hiding this comment

opbld30 commented Nov 18, 2021

✅ Validation status: passed

opbld32 commented Nov 19, 2021

✅ Validation status: passed

Rick-Kirkham commented Nov 15, 2021 •

edited