Automated Testing in Microsoft Dynamics 365 Business Central: Efficiently automate test cases for faster development cycles with less time needed for manual testing, 2nd Edition

Cover
Title
Copyright and Credits
Table of Contents
Section 1: Automated Testing – A General Overview
Chapter 1: Introduction to Automated Testing
	Why automated testing?
		Why not?
		Why yes?
		Some more arguments
		Silver bullet?
	When to use automated testing?
		After go-live bug fixing
		Buggy code
		Frequently modified code
		Business-critical code being changed
		Refactoring existing code
		New feature development
		Microsoft updates
	What is automated testing?
		Some more notes on automated tests
	Summary
Chapter 2: Test Automation and Test-Driven Development
	TA versus TDD
	What is TDD?
		Only two rules to the game
		TDD – the red-green-refactor mantra
		TDD – taking small steps
		TDD – the benefits
	TDD and Microsoft Dynamics 365 Business Central
		Is TDD in Business Central possible?
		Don't know how to start?
		TDD in Business Central – by example
		TDD – all the way?
	TDD – inside-out or outside-in
	Summary
	Further reading
Section 2:Automated Testing in Microsoft Dynamics 365 Business Central
Chapter 3: The Testability Framework
	Technical requirements
	The five pillars of the testability framework
		Pillar 1 – Test codeunits and test functions
		Pillar 2 – The asserterror keyword
		Pillar 3 – Handler functions
		Pillar 4 – Test runner and test isolation
		Pillar 5 – Test pages
	Summary
Chapter 4: The Test Tools, Standard Tests, and Standard Test Libraries
	Technical requirements
	Test Tools
		Adding tests to a test suite
		Running the tests
	Standard tests
		Base Application tests
		Categorization by FEATURE
	Standard libraries
		Finding useful standard helper functions
		Some generic and very useful standard libraries
	Summary
Section 3:Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
Chapter 5: Test Plan and Test Design
	No plan, no test
	Setting up a test plan
		Break down your application or feature
	Test case design patterns
		Four-phase testing
		Acceptance Test-Driven Development
		A note on test verification
		Applying test case design patterns successfully
	Test data setup design patterns
		Test fixture, data agnostics, and prebuilt fixture
		Test fixture and test isolation
		Shared fixture implementation
		Fresh fixture implementation
		Applying test data setup design patterns successfully
	Using customer wish as test plan
	And what about unit and functional tests?
		Test case design pattern and unit tests
		Functional testing versus integration testing
	Summary
	Further reading
Chapter 6: From Customer Wish to Test Automation – the Basics
	Technical requirements
	From customer wish to test automation
		Data model
		Business logic
		Converting our customer wish into a test plan and test design
	Test example 1 – a first headless test
		Customer wish
		Application code
		Test code
		Test execution
	Test example 2 – a first positive-negative test
		Test code steps
		Create a test codeunit
		Test execution
	Test example 3 – a first UI test
		Customer wish
		Test code
		Test execution
	Headless versus UI
	Summary
Chapter 7: From Customer Wish to Test Automation – Next Level
	Technical requirements
	Sales documents, customer template, and warehouse shipment
	Test example 4 – how to set up a shared fixture
		Customer wish
		Application code
		Test Code
		Test execution
	Test example 5 – how to parameterize tests
		Customer wish
		Application code
		Test code
		Test execution
		A missing scenario?
	Test example 6 – how to hand over data to UI handlers
		Customer wish
		Test code
		Test execution
	Summary
Chapter 8: From Customer Wish to Test Automation – the TDD way
	Technical requirements
	TDD and our test examples
	Test example 7 – how to refactor your code
		Smell of duplication 1
		Smell of duplication 2
		Some more duplications?
		Refactoring application code, not covered by tests yet
	Test example 8 – how to test a report
		Customer wish
		Step 1 – Take a test from the test list and write the test code
		Step 2 – Compile test code yielding red as application code is not yet there
		Step 3 – Add just enough application code
		Step 4 – Run test seeing it probably fail
		Step 3 bis – Add just enough application code
		Step 4 bis – Run test seeing it probably fail
		Step 5 – Adjust the application code just enough to make it pass
		Step 6 – Refactor your code and rerun the test to prove all code is still well
		Test the test
	Test example 9 – how to test with permissions
		Step 1 – Take a test from the test list and write the test code
		Step 2 – Compile test code yielding red as application code is not yet there, and Step 3 – Add just enough application code
		Step 4 – Run the test seeing it probably fail
		Step 5 – Adjust application code just enough to make it pass, and Step 6 – Refactor your code and rerun the test to prove all code is still well
		Step 7 – Move to the next test on the list and repeat from Step 1
		Continue the red-green-refactor mantra
		Some notes on testing permissions and the version of Business Central
	Summary
Section 4:Integrating Automated Tests in Your Daily Development Practice
Chapter 9: How to Integrate Test Automation in Daily Development Practice
	Technical requirements
	Casting the customer wish into ATDD scenarios
		ATDD.TestScriptor
	Learning and improving by taking small steps
	Making the test tool, and some more, your friend
		Extending the test tool
		AL Test Runner
		Code Coverage
	Maintaining your test code
	Organizing your extensions
	Integrating with the daily build system
		Using pipelines
		Or not using pipelines
	Summary
Chapter 10: Getting Business Central Standard Tests Working on Your Code
	Technical requirements
	Why use the standard tests?
	Executing standard tests against your code
		Executing Tests-VAT
		What does this tell us?
		Only selecting tests from Tests-VAT
		Running tests using pipelines
	Fixing failing standard tests
		Attacking the error
		Fixing the error
		Running the failing tests again
	Disabling failing tests
		Syntax of DisabledTests.json
	It's all about data
		Executing and fixing Tests-Fixed Asset
		Running tests using pipelines
	Is it all really about data?
	Summary
Section 5:Advanced Topics
Chapter 11: How To Construct Complex Scenarios
	Technical requirements
	What makes a scenario complex?
		Data setup
		Verification
		End-to-end code execution path
		Dependencies on other systems
	Composing complex scenarios
		Finding common ground – steps 1, 2, 3, and 4
		Deconstructing your scenario – steps 1, 2, 3, and 4
		Using flowcharts – steps 1 and 3
		Using Code Coverage – steps 1 and 3
		Using standard helper functions – steps 5, 6, and 7
	Creating reusable parts
	Test example 10 – how to construct an extensive scenario
		Customer wish
		Application code
		Test code
		Test execution
	Summary
Chapter 12: Writing Testable Code
	Technical requirements
	What is testable code?
	How to make your code testable?
		Coding techniques
		Some notes on refactoring your code so it is testable
	Test example 11 – how to unit test event subscribers' logic
		Customer wish
		Application code
		Test code
		Test execution
	Summary
	Further reading
Chapter 13: Testing Incoming and Outgoing Calls
	Technical requirements
	Testing incoming calls
		Technical challenges
		Examples of standard API tests
	Testing outgoing calls
		Test Doubles
		Replacing a server with a test double – dependency injection
		Some more notes on mock and mocking
		Examples of standard tests with test doubles replacing external components
	Test example 12 – testing incoming calls: Lookup Value API
		Application code
		Test scenarios
		Test Code – [SCENARIO #0200] Get lookup value
		Test Code – [SCENARIO #0202] Modify lookup value
		Test preparation
		Test execution
	Test example 13 – VAT Registration No. validation
		Application code
		Test code
		Test execution
	Summary
Section 6:Appendix
Appendix: Getting Up and Running with Business Central, VS Code, and the GitHub Project
	Setting up your Business Central environment
		Setting up Business Central from a product DVD
		Setting up Business Central in a container
	The GitHub repository
		Structure of the GitHub repository
		Chapter 02
		Chapter 03
		Excel Sheets
		Chapter 06 (LookupValue Extension)
		Chapter 07 (LookupValue Extension)
		Chapter 08 (LookupValue Extension)
		Chapter 09 (LookupValue Extension)
		Chapter 10 (LookupValue Extension)
		Chapter 11 (LookupValue Extension)
		Chapter 12 (LookupValue Extension)
		Chapter 13 (LookupValue Extension)
		Scripts
		Chapter 13 (VAT Registration No. Validation)
		LookupValue Extension
		Graphics
	Setting up VS Code
		VS Code project
	Notes on the AL code
		Prefix or suffix
		Word wrap
Index