舉報(bào) 
會(huì)員
Automated Testing in Microsoft Dynamics 365 Business Central
Dynamics365BusinessCentralisthenewcloud-basedSaaSERPpropositionfromMicrosoft.It’snotassimpleasitusedtobewaybackwhenitwascalledNavigator,NavisionFinancials,orMicrosoftBusinessSolutions-Navision.Ourdevelopmentpracticesarebecomingmoreformal,andwiththis,thecallfortestautomationispressingonus.ThisbookwillteachyoutoleveragetestingtoolsavailablewithDynamics365BusinessCentraltoperformautomatedtesting.We’llbeginwithaquickintroductiontoautomatedtesting,followedbyanoverviewoftestautomationinDynamics365BusinessCentral.Thenyou’lllearntodesignandbuildautomatedtestsandwe’llgothroughsomeefficientmethodstogetfromrequirementstoapplicationandtestingcode.Lastly,you’lllearntoincorporateyourownandMicrosofttestsintoyourdailydevelopmentpractice.Bytheendofthebook,you’llbeabletowriteyourownautomatedtestsforDynamics365BusinessCentral.
最新章節(jié)
- Leave a review - let other readers know what you think
- Other Books You May Enjoy
- Word wrap
- Prefix or suffix
- VS Code versus C/SIDE
- Notes on the AL code
品牌：中圖公司
上架時(shí)間：2021-06-24 12:21:56
出版社：Packt Publishing
本書數(shù)字版權(quán)由中圖公司提供，并由其授權(quán)上海閱文信息技術(shù)有限公司制作發(fā)行
- Leave a review - let other readers know what you think 更新時(shí)間：2021-06-24 14:57:26
- Other Books You May Enjoy
- Word wrap
- Prefix or suffix
- VS Code versus C/SIDE
- Notes on the AL code
- LookupValue Test Extension (test only)
- Chapter 9 (LookupValue Extension)
- Chapter 7 (LookupValue Extension) - refactored and completed
- Chapter 7 (LookupValue Extension)
- Chapter 6 (LookupValue Extension)
- Chapter 5 (LookupValue Extension)
- LookupValue Extension (app only)
- ATDD Scenarios
- Chapter 2
- Structure of the GitHub repository
- The GitHub repository
- app.json
- launch.json
- VS Code project
- VS Code and AL development
- Setting Up VS Code and Using the GitHub Project
- Summary
- TDD and our test examples
- TDD red-green-refactor
- TDD a short description
- Test-Driven Development
- Summary
- Is it all really about data?
- Applying the Handled pattern
- Making your code testable
- It's all about data
- Viewing the call stack from the test tool
- Running the failing tests again
- Fixing the error
- Attacking the error
- Fixing failing standard tests
- What does this tell us?
- Executing standard test
- Why use the standard tests?
- Getting Business Central Standard Tests Working on Your Code
- Summary
- Extensions and tests
- Maintaining your test code
- Integrating with daily build
- Extending the test tool
- Test coverage map
- Making the test tool your friend
- Taking small steps
- Casting the customer wish into ATDD scenarios
- How to Integrate Test Automation in Daily Development Practice
- Section 4: Integrating Automated Tests in Your Daily Development Practice
- Summary
- Refactoring
- Adjust the test so the verification errs
- Test the test
- Test execution
- CreateWarehouseShipmentFromSalesOrder
- VerifyLookupValueOnWarehouseShipmentLine
- Initialize
- Construct the real code
- Create embed and write
- Test code
- Application code
- Customer wish
- Test example 8 – how to construct an extensive scenario
- Adjust the test so the verification errs
- Test the test
- Test execution
- Construct the real code
- Create embed and write
- Test code
- Application code
- Customer wish
- Test example 7 – how to test a report
- From Customer Wish to Test Automation - And Some More
- Summary
- Test the test
- Test execution
- Dequeue
- Enqueue
- Construct the real code
- Create embed and write
- Test code
- Customer wish
- Test example 6 – how to hand over data to UI handlers
- A missing scenario?
- Test the test
- Test execution
- Construct the real code
- Create embed and write
- Test code
- Application code
- Customer wish
- Test example 5 – how to parametrize tests
- Test the test
- Test execution
- Construct the real code
- Write your test story
- Embed the customer wish into a test function
- Create a test codeunit
- Test Code
- Application code
- Customer wish
- Test example 4 – how to set up a shared fixture
- Sales documents customer template and warehouse shipment
- From Customer Wish to Test Automation - Next Level
- Summary
- Headless versus UI
- Adjust the test so the verification errs
- Test the test
- Test execution
- SetLookupValueOnCustomerCard
- CreateCustomerCard
- Construct the real code
- Write your test story
- Embed the customer wish into a test function
- Create a test codeunit
- Test code
- Application code
- Customer wish
- Test example 3 – a first UI test
- Removing asserterror
- Adjust the test so the verification errs
- Test the test
- Test execution
- VerifyNonExistingLookupValueError
- Construct the real code
- Write your test story
- Embed the customer wish into a test function
- Create a test codeunit
- Steps to take
- Test code
- Test example 2 – a first positive-negative test
- Adjust the test so the verification errs
- Test the data being created
- Test the test
- Test execution
- VerifyLookupValueOnCustomer
- SetLookupValueOnCustomer
- CreateCustomer
- CreateLookupValueCode
- Construct the real code
- Write your test story
- Embed the customer wish into a test function
- Create a test codeunit
- Steps to take
- Test code
- Application code
- Complete scenario
- THEN
- WHEN
- GIVEN
- SCENARIO
- FEATURE
- Customer wish
- Test example 1 – a first headless test
- Implementing a defined customer wish
- LookupValue extension
- Business logic
- Data model
- From customer wish to test automation
- From Customer Wish to Test Automation - The Basics
- Summary
- Using customer wish as test design
- Fresh fixture implementation
- Shared fixture implementation
- Test fixture and test isolation
- Test fixture data agnostics and prebuilt fixture
- Understanding test data setup design patterns
- A note on test verification
- Acceptance Test-Driven Development
- Understanding test case design patterns
- No design no test
- Test Design
- Section 3: Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
- Summary
- Standard libraries
- Categorization by FEATURE
- Standard tests
- Test Tool
- The Test Tool and Standard Tests
- Summary
- Pillar 5 – Test pages
- Test isolation
- Test runner
- Pillar 4 – Test runner and test isolation
- Pillar 3 – handler functions
- Pillar 2 – asserterror
- Test functions
- Test codeunits
- Pillar 1 – Test codeunits and test functions
- The five pillars of the testability framework
- The Testability Framework
- Section 2: Automated Testing in Microsoft Dynamics 365 Business Central
- Summary
- What is automated testing?
- Microsoft updates
- New feature development
- Refactoring of existing code
- Business-critical code being changed
- Frequently modified code
- Buggy code
- After go-live bug fixing
- When to use automated testing
- Silver bullet?
- Test automation is required
- Shorter update cycles
- Once the learning curve is over it will often be quicker than manual testing
- Reduced risks and higher satisfaction
- Nobody loves testing
- Some more arguments
- Automated tests are code too
- Keep on handling different projects because of test automation
- Test automation will free up time for everyday business
- Having a hard time finding people – start automating your tests
- Relying on customers to do the testing isn't a great idea
- Dynamics 365 Business Central platform enables test automation
- Drive testing upstream and save costs
- Why yes?
- Why not?
- Why automated testing?
- Introduction to Automated Testing
- Section 1: Automated Testing - A General Overview
- Reviews
- Get in touch
- Conventions used
- Download the color images
- Download the example code files
- To get the most out of this book
- What this book covers
- Who this book is for
- Preface
- Packt is searching for authors like you
- About the reviewers
- About the author
- Contributors
- Foreword
- Packt.com
- Why subscribe?
- About Packt
- Dedication
- Automated Testing in Microsoft Dynamics 365 Business Central
- Copyright and Credits
- Title Page
- coverpage
- coverpage
- Title Page
- Copyright and Credits
- Automated Testing in Microsoft Dynamics 365 Business Central
- Dedication
- About Packt
- Why subscribe?
- Packt.com
- Foreword
- Contributors
- About the author
- About the reviewers
- Packt is searching for authors like you
- Preface
- Who this book is for
- What this book covers
- To get the most out of this book
- Download the example code files
- Download the color images
- Conventions used
- Get in touch
- Reviews
- Section 1: Automated Testing - A General Overview
- Introduction to Automated Testing
- Why automated testing?
- Why not?
- Why yes?
- Drive testing upstream and save costs
- Dynamics 365 Business Central platform enables test automation
- Relying on customers to do the testing isn't a great idea
- Having a hard time finding people – start automating your tests
- Test automation will free up time for everyday business
- Keep on handling different projects because of test automation
- Automated tests are code too
- Some more arguments
- Nobody loves testing
- Reduced risks and higher satisfaction
- Once the learning curve is over it will often be quicker than manual testing
- Shorter update cycles
- Test automation is required
- Silver bullet?
- When to use automated testing
- After go-live bug fixing
- Buggy code
- Frequently modified code
- Business-critical code being changed
- Refactoring of existing code
- New feature development
- Microsoft updates
- What is automated testing?
- Summary
- Section 2: Automated Testing in Microsoft Dynamics 365 Business Central
- The Testability Framework
- The five pillars of the testability framework
- Pillar 1 – Test codeunits and test functions
- Test codeunits
- Test functions
- Pillar 2 – asserterror
- Pillar 3 – handler functions
- Pillar 4 – Test runner and test isolation
- Test runner
- Test isolation
- Pillar 5 – Test pages
- Summary
- The Test Tool and Standard Tests
- Test Tool
- Standard tests
- Categorization by FEATURE
- Standard libraries
- Summary
- Section 3: Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
- Test Design
- No design no test
- Understanding test case design patterns
- Acceptance Test-Driven Development
- A note on test verification
- Understanding test data setup design patterns
- Test fixture data agnostics and prebuilt fixture
- Test fixture and test isolation
- Shared fixture implementation
- Fresh fixture implementation
- Using customer wish as test design
- Summary
- From Customer Wish to Test Automation - The Basics
- From customer wish to test automation
- Data model
- Business logic
- LookupValue extension
- Implementing a defined customer wish
- Test example 1 – a first headless test
- Customer wish
- FEATURE
- SCENARIO
- GIVEN
- WHEN
- THEN
- Complete scenario
- Application code
- Test code
- Steps to take
- Create a test codeunit
- Embed the customer wish into a test function
- Write your test story
- Construct the real code
- CreateLookupValueCode
- CreateCustomer
- SetLookupValueOnCustomer
- VerifyLookupValueOnCustomer
- Test execution
- Test the test
- Test the data being created
- Adjust the test so the verification errs
- Test example 2 – a first positive-negative test
- Test code
- Steps to take
- Create a test codeunit
- Embed the customer wish into a test function
- Write your test story
- Construct the real code
- VerifyNonExistingLookupValueError
- Test execution
- Test the test
- Adjust the test so the verification errs
- Removing asserterror
- Test example 3 – a first UI test
- Customer wish
- Application code
- Test code
- Create a test codeunit
- Embed the customer wish into a test function
- Write your test story
- Construct the real code
- CreateCustomerCard
- SetLookupValueOnCustomerCard
- Test execution
- Test the test
- Adjust the test so the verification errs
- Headless versus UI
- Summary
- From Customer Wish to Test Automation - Next Level
- Sales documents customer template and warehouse shipment
- Test example 4 – how to set up a shared fixture
- Customer wish
- Application code
- Test Code
- Create a test codeunit
- Embed the customer wish into a test function
- Write your test story
- Construct the real code
- Test execution
- Test the test
- Test example 5 – how to parametrize tests
- Customer wish
- Application code
- Test code
- Create embed and write
- Construct the real code
- Test execution
- Test the test
- A missing scenario?
- Test example 6 – how to hand over data to UI handlers
- Customer wish
- Test code
- Create embed and write
- Construct the real code
- Enqueue
- Dequeue
- Test execution
- Test the test
- Summary
- From Customer Wish to Test Automation - And Some More
- Test example 7 – how to test a report
- Customer wish
- Application code
- Test code
- Create embed and write
- Construct the real code
- Test execution
- Test the test
- Adjust the test so the verification errs
- Test example 8 – how to construct an extensive scenario
- Customer wish
- Application code
- Test code
- Create embed and write
- Construct the real code
- Initialize
- VerifyLookupValueOnWarehouseShipmentLine
- CreateWarehouseShipmentFromSalesOrder
- Test execution
- Test the test
- Adjust the test so the verification errs
- Refactoring
- Summary
- Section 4: Integrating Automated Tests in Your Daily Development Practice
- How to Integrate Test Automation in Daily Development Practice
- Casting the customer wish into ATDD scenarios
- Taking small steps
- Making the test tool your friend
- Test coverage map
- Extending the test tool
- Integrating with daily build
- Maintaining your test code
- Extensions and tests
- Summary
- Getting Business Central Standard Tests Working on Your Code
- Why use the standard tests?
- Executing standard test
- What does this tell us?
- Fixing failing standard tests
- Attacking the error
- Fixing the error
- Running the failing tests again
- Viewing the call stack from the test tool
- It's all about data
- Making your code testable
- Applying the Handled pattern
- Is it all really about data?
- Summary
- Test-Driven Development
- TDD a short description
- TDD red-green-refactor
- TDD and our test examples
- Summary
- Setting Up VS Code and Using the GitHub Project
- VS Code and AL development
- VS Code project
- launch.json
- app.json
- The GitHub repository
- Structure of the GitHub repository
- Chapter 2
- ATDD Scenarios
- LookupValue Extension (app only)
- Chapter 5 (LookupValue Extension)
- Chapter 6 (LookupValue Extension)
- Chapter 7 (LookupValue Extension)
- Chapter 7 (LookupValue Extension) - refactored and completed
- Chapter 9 (LookupValue Extension)
- LookupValue Test Extension (test only)
- Notes on the AL code
- VS Code versus C/SIDE
- Prefix or suffix
- Word wrap
- Other Books You May Enjoy
- Leave a review - let other readers know what you think 更新時(shí)間：2021-06-24 14:57:26
