Microsoft Dynamics NAV
Test Automation Suite
Andrei Panko
Program manager
Why?
Microsoft has been releasing
new versions more frequently
We are also releasing cumulative
updates every month
We need to ensure that you can also deliver new functionality to your
customers with as little effort as possible and with as little risk as possible
Lack of automation
makes testing
expensive and
tedious
Merges often
introduce new bugs
that can be difficult to
find
You have to spend a
lot of time testing
instead of
billing it to
customers
Why?
We have the same challenges!
NAV 2013
NAV 2013 R2
4 versions in
the market
1 version in
development
20 countrybuilds + W1
for each
version
NAV 2015
NAV 2016 W1
Critical Update
HotFix
AT
CA
DE
DK
GB
FR
IT
NL
SE
US
NAV V-NEXT
Features
What?
Tools for managing and executing tests: UI + CMD
More than 15.000 regression tests that we run daily for each country-specific
build
Helper libraries for improving test development by reusing common
functionality
Samples and documentation
Tools for capturing code coverage and selecting relevant tests out of available
tests
Try to run tests released with Test Automation Suite on your product/solution
Exclude failing tests (if any)
Set up test execution on a regular basis
Do not submit code that decreases test pass rate and test coverage rate
Improve test coverage of your product/solution by adding tests
Try to run tests released with Test Automation Suite on your product/solution
Exclude failing tests (if any)
Set up test execution on a regular basis
Do not submit code that decreases test pass rate and test coverage rate
Improve test coverage of your product/solution by adding tests
Try to run tests released with Test Automation Suite on your product/solution
Exclude failing tests (if any)
Set up test execution on a regular basis
Do not submit code that decreases test pass rate and test coverage rate
Improve test coverage of your product/solution by adding tests
What?
Integrated with
the application
Used to
measure test
coverage
Used to create
Test Coverage
Map
Gives overview
of executed
code
Try to run tests released with Test Automation Suite on your product/solution
Exclude failing tests (if any)
Set up test execution on a regular basis
Do not submit code that decreases test pass rate and test coverage rate
Improve test coverage of your product/solution by adding tests
During feature development: Transform typical acceptance scenarios into
tests.
Test regression: When a bug is fixed, we consider it a best practice to create
a test (or several tests).
Test completeness: We perform ongoing efforts in test completion and
improving test coverage rate.
83% Test code executed by
this function is from libraries
(approx. 250 lines of 300)
Try to run tests released with Test Automation Suite on your product/solution
Exclude failing tests (if any)
Set up test execution on a regular basis
Do not submit code that decreases test pass rate and test coverage rate
Improve test coverage of your product/solution by adding tests
Learn more
http://aka.ms/NAVGetReady