Important: Test Base for Microsoft 365 will transition to end-of-life (EOL) on May 31, 2024. We're committed to working closely with Test Base customers to provide support and guidance to make the transition as smooth as possible. If you have any questions or concerns, or need assistance, please submit a support request. |
To help you quickly take advantage of Test Base, we are now offering open source Test Base samples and tools on GitHub, making it easier than ever to build Test Base packages, integrate Test Base into your CI/CD, and query test results by API.
Keeping applications resilient to platform and dependency changes need not be tedious. As developers or IT professionals, you have traditionally gained confidence in application resilience through thorough testing, much of it manual or costly to configure. You have likely used dedicated test labs where you have maintained machines that must be regularly patched and decommissioned every few years. Hand-coding test cases and making sure they are executed against a growing test matrix have taken up a lot of time.
With Test Base for Microsoft 365, these can be things of the past. Once onboarded to Test Base, your apps will be tested with no effort on your part. Every month, as Windows updates, a test run will be kicked off and these applications will be installed and launched on test virtual machines on Azure. Using machine learning, Test Base will observe the behavior of these apps before and after the updates are applied to the virtual machine. Any observable regression in an app – either because of an app change or a platform change - will cause the corresponding test to fail. With the help of the results in the Test Base portal, you can then be armed with the data you need to understand the exact nature of the failure.
Get inspiration and guidance from the Test Base GitHub repository
The Test Base GitHub repo provides best practice, samples, and feedback channels to enhance your experience when using Test Base for Microsoft 365.
Best practices
Utilize best practices to see how to integrate Test Base to CI/CD using GitHub Actions in four steps. Once you integrate Test Base with your own CI/CD, the new version of your packages will be uploaded to Test Base automatically. Here’s how to give it a try:
- Prepare the application and related scripts.
- Onboard your application to Test Base.
- Use Test Base APIs to query your application’s test results.
- Set up Test Base as part of your CI/CD pipeline.
Package samples
The Test Base GitHub repo offers a variety of sample packages that can give you some inspiration when building your own Test Base packages:
- Calculator-Appium-Charp-Sample
- Calculator-Appium-Java-Sample
- Calculator-Appium-Python-pytest-Sample
- Calculator-Appium-Python-unittest-Sample
- Calculator-MSTest-Sample
- Calculator-OOB-Sample
- StoreAPP-OOB-Sample
How to contribute to the rept
We are listening. Follow the contributing guidelines to file bugs, raise feature requests, and give us feedback.
Become an active Test Base GitHub Community member
Test Base enables testing that is intelligent and convenient, and that can happen from anywhere you are in the world. We are actively engaging with application developers and enterprise organizations like you to add more value and make testing easier. We would like to invite you to come to engage with us and the broader Test Base developer community through Test Base discussions on GitHub and providing feedback on your Test Base experience (Azure portal, sample packages, SDK samples, etc.). We also invite you to:
- Share ideas and communicate with fellow community members.
- Ask questions.
- Become an evangelist and recommending us to others.
We are looking forward to seeing you share your experiences, connect with others, and build an active Test Base GitHub community!