Skip to main content

Testing and to find reason of an issue tips for juniors

 In this blog you can find some testing tips that may help.


1. Start with basic testing:


If you are testing the invoicing process,use one order one line to test first. 


2. Test with multiple transactions.


If you are testing the invoicing process and passed the basic testing, test with multiple transactions like multiple lines, multiple orders.


3. Test from the start


If any of the cases failed during testing, test from the start.


4. Document Testing Operations


You must document the cases before you start the testing, but can be added new ones during testing. Document details. This documentation can be in written or using videos or other tools.


5. Test with different data.


Do not test with the same data like to fill qty as  any amount as 100. Use decimals etc for testing purposes.


 6. Test to have error messages. Test like users.


Test like a user and do incorrect actions to have error messages. Forget to activate the account and see what happens.


7. Do the partial testing.


Check if partial processes do work.


8. Check reports


After you proceed, do check the reflection for the reports.


9. Do test the whole flow.


Do test the whole flow if it does effect prior or post processes.

Labels:

Comments

Post a Comment

Popular posts from this blog

Manage ERP with Success - Blockers of Success

  To manage an ERP process with success is not easy at all. Even there has been processes that have been published by companies, it is mostly depend on the people. In this blog , I am going to share the reasons I see as blockers of during the projects. This is not a scientific measure but just my opinions. Sales Team:  ERP project starts from even before the sales documents are finalized. So company needs (not user/not management etc.) need to be understood wisely and to be checked if the tools can manage these needs and details need to be documented in the contract. Expectations:  Unfortunately, ERP is a software but not a hardware. So expectation management is very important. If it was a hardware, then you will be able to return and to document specific details.  Project Team:  By project team, mostly we understand the consultancy firm but project team does consist of also from customer project managers, users, power users etc. All project team need to be well...
Post a Comment
Read more

Allocation ways in D365 FO

 When we say allocations of expenses through accounts and dimension, there are various ways that can be used in D365 FO. In this blog you can find these ways and their differences from one to another. Cost Accounting Module:  If you do not need/require to post any transaction or you think that there will be too many transactions appear on voucher transactions, then you can use cost accounting module to report on your balances. This module works separate from the GL module. Data is transferred from GL module and you prepare your allocation rules in this module and do your reporting. also you can use this module for to report different versions. Allocation Rules : You can define allocation rules and within the period you want to use, system will allocate the balance to the relevant account and dimensions. The pros of this type is that, you can trigger and change the rules whenever you want to . The cons of this type is, you need to trigger each rule one by one, wait for the repo...
Post a Comment
Read more

Fast Track Recognized Solution Architect

      You may be a fast track recognized solution architect. Fast track is best practices to succeed on the project.(Called Success by Design) This process is documented by the fast track solution architects. When applied to be a fast track solution architect, evaluation is done by D365 engineering team.      Earning Criteria The architect must be nominated by the partner Must have a minimum of 5 years of experience with Dynamics CRM or ERP products Must have a minimum of 3 years of experience as a solution architect Must be the lead architect on at least 2 FastTrack governed customer implementation projects Must be responsible for the architecture and design of at least 2 FastTrack governed customer implementation projects Even if you can not fill these requirements above, you are still able to read the detailed documentation from the links below to succeed. https://docs.microsoft.com/en-us/dynamics365/fasttrack/implementation-guide/overview https://www.d3...
Post a Comment
Read more