Sorry, my question included Integration testing, so feedback title should be "Would you please provide information about Unit test and Integration test?"

@NT-D Thanks for asking about this. I'm checking into this with my team and I'll see if I can give you an update soon.

Thanks.

@NT-D We don't yet have any docs on this type of testing but we're working on it. For now, I'll put this issue on hold and we'll respond once we've put together some guidance for this area.

Thanks.

Thank you @ElizabethSamuel-MSFT. I'm looking forward to see update :)

All Outlook add-ins docs have just been moved out of this repo and into the OfficeDev/office-js-docs-pr repo, so I'm transferring this add-ins-related issue there as well.

@kbrandl Which issue can I see progress in OfficeDev/office-js-docs-pr?

@NT-D I'm no longer a Microsoft employee, so cannot answer your question. @ElizabethSamuel-MSFT are you able to provide input here?

Thanks, @kbrandl.

@NT-D For now, there's no further update. You can keep track with this same issue as it's now in the office-js-docs-pr repo.

Thanks.

It has been almost three years since #584, so to me it seems that supporting testing, CI/CD is not a priority for Microsoft. If that's so then fine I find other means to test my addin. But right now Microsoft does not clearly state that they are not going to provide these features in the near future. This situation is difficult for us because we would not like to invest a lot of time in developing a non-standard test solution if Microsoft release a framework for testing addins in all the various environments etc. So it would be very helpful if the team could provide us with a realistic timeline (this year, next year, never, no decision has been made).

Bump

Hi everyone,

We appreciate all the discussion and feedback requesting testing solutions for Office Add-ins and Office JS. Unfortunately, there are no automated or unit testing solutions that we provide at this time. We're working on a solution, but have no concrete implementation or release details to share at this time. We realize this is an unsatisfying answer, but we feel it’s better to be clear about the support story, rather than to create false expectations.

We are moving the discussion to M365 Developer Platform Ideas. For the primary concern around standardized testing, please upvote and comment on this idea: Standard way to unit test and mock office-js API. For the other related requests that have accumulated on this issue, we also ask that you take your requests to the M365 Developer Platform Ideas and submit them as ideas (or upvote existing ones). This will help us prioritize things in an orderly fashion.

If there are other issues about the documentation that have been raised in this thread but were not addressed, please create a new issue to track each specific problem.

Thank you.

We now have documentation for unit testing and mocking in Office.js.

Unit testing in Office Add-ins

Thank you for the efforts. However, IMHO we still need to test the office API (if possible). All methods are manually mocked in the aforementioned approach so we do not really test much functionality...