use_azure_pipelines()

.Rbuildignore

@@ -14,3 +14,4 @@
 ^\.github$
 ^pkgdown$
 ^\.covrignore$
+^azure-pipelines\.yml$

README.md

@@ -4,6 +4,9 @@
 [![CRAN status](https://www.r-pkg.org/badges/version/roxygen2)](https://CRAN.R-project.org/package=roxygen2)
 [![Travis build status](https://travis-ci.org/r-lib/roxygen2.svg?branch=master)](https://travis-ci.org/r-lib/roxygen2)
 [![Codecov test coverage](https://codecov.io/gh/r-lib/roxygen2/branch/master/graph/badge.svg)](https://codecov.io/gh/r-lib/roxygen2?branch=master)
+[![Azure pipelines build status](https://img.shields.io/azure-devops/build/r-lib/roxygen2/2)](https://dev.azure.com/r-lib/roxygen2/_build/latest?definitionId=1&branchName=master)
+[![Azure pipelines test status](https://img.shields.io/azure-devops/tests/r-lib/roxygen2/2?color=brightgreen&compact_message)](https://dev.azure.com/r-lib/roxygen2/_build/latest?definitionId=1&branchName=master)
+[![Azure pipelines coverage status](https://img.shields.io/azure-devops/coverage/r-lib/roxygen2/2)](https://dev.azure.com/r-lib/roxygen2/_build/latest?definitionId=1&branchName=master)
 <!-- badges: end -->
 
 The premise of roxygen2 is simple: describe your functions in comments next to their definitions and roxygen2 will process your source code and comments to automatically generate `.Rd` files in `man/`, `NAMESPACE`, and, if needed, the `Collate` field in `DESCRIPTION`.

azure-pipelines.yml

@@ -0,0 +1,12 @@
+# R package
+# Test an R package
+
+resources:
+  repositories:
+    - repository: r-azure-pipelines
+      type: github
+      name: r-lib/r-azure-pipelines
+      endpoint: r-lib
+
+jobs:
+  - template: azure-tidyverse.yml@r-azure-pipelines

tests/testthat.R

@@ -1,4 +1,8 @@
 library(testthat)
 library(roxygen2)
 
-test_check("roxygen2")
+if (requireNamespace("xml2")) {
+  test_check("roxygen2", reporter = MultiReporter$new(reporters = list(JunitReporter$new(file = "test-results.xml"), CheckReporter$new())))
+} else {
+  test_check("roxygen2")
+}