Tag: test Cases

This is a NetSuite – Tracktrace integration. Locations created in the NetSuite account are synced to Track Traces in real time. If the location is deleted or inactivated in NetSuite, it is removed from Tracktrace also

Task Description Sales order sync from NetSuite to TrackTrace. When a Sales order is created in the NetSuite it is synced to track trace and a UUID is created. When an item line is added or removed from the Sales order, then it’s synced to track trace. is closed in the NetSuite, Also deleting a… Continue reading Testcase Documentation -SSRX-489

Testing the integration of NetSuite with other systems requires a comprehensive test suite to ensure the data flows seamlessly between the systems. Here are some test cases for NetSuite integration:  Authentication: Verify that the NetSuite integration is authenticated correctly and that the credentials are valid.  Data mapping: Verify that the data is accurately mapped between… Continue reading Important Testcases for NetSuite Integration

Task Description- If Sales orders with Canada as the country in ship to address, then it will have the custom check box INCLUDE: CANADA CONSOLIDATED INVOICE checked and the same check box in IF of the sales order will also be checked. These SO will be listed in Canada consolidated invoice. Clicking the sent email… Continue reading DVTB-297 Testcase Documentation

Test case documentation is important for manual testing for several reasons Ensures completeness: Test case documentation ensures that all the features and functions of the application under test have been tested. It helps testers to make sure that no critical functionality is left untested. Provides clarity: Test case documentation provides clarity on the expected behavior of the application under test. It helps testers to understand what the application should do and how it should behave in different scenarios. Helps in regression testing: Test case documentation provides a record of the tests that have been performed. This makes it easier for testers to perform regression testing in the future and ensure that new changes to the application do not break existing functionality. Facilitates collaboration: Test case documentation helps testers and other stakeholders to collaborate more effectively. It helps to ensure that everyone has a shared understanding of the application under test and the tests that need to be performed. Improves accountability: Test case documentation helps to establish accountability for testing. It ensures that testers are responsible for testing specific features or functions and helps to identify the root cause of defects if they are found In summary, test case documentation is important for manual testing because it ensures completeness, provides clarity, facilitates collaboration, helps in regression testing, and improves accountability. It helps to ensure that the application under test meets the requirements and is of high quality A Test Case Template contains -> Name… Continue reading Importance of Test Case Documentation

Task Description– workflow for approval of JE and approval process are user-specific. The user as the creator can create a Journal entry from any role which have access to JE and the user as an approver can approve or reject JE from any role which has access to JE. If the approver rejects the JE,… Continue reading ZCPL 35 -Test case documentation