API and services test automation involves using tools and scripts to automate the testing of application programming interfaces (APIs) and web services. This type of testing is often used to verify the functionality, reliability, and performance of these critical components of modern software applications. The primary goal of API and services test automation is to… Continue reading API and Services Test Automation
Author: Agnel Anjuluse
Test sigma and Testing Whiz
Testsigma is a cloud-based test automation platform that allows software testing teams to create, execute and manage automated tests for web, mobile, and desktop applications. It offers a codeless testing approach where users can create test cases using natural language, making it easy for non-technical team members to create and run automated tests. Testsigma uses… Continue reading Test sigma and Testing Whiz
Equivalence Partitioning and Boundary Value testing
Boundary testing Boundary testing is the process of testing between extreme ends or boundaries between partitions of the input values. So, these extreme ends like Start- End, Lower- Upper, Maximum-Minimum, Just Inside-Just Outside values are called boundary values and the testing is called “boundary testing”. The basic idea in normal boundary value testing is to… Continue reading Equivalence Partitioning and Boundary Value testing
Wave
In NetSuite, a “Wave” refers to a group of sales orders or transfer orders that are combined and processed together for fulfillment in the warehouse. This allows businesses to optimize their order fulfillment process and increase efficiency. Creating a wave in NetSuite: Create a new wave: To create a new wave, go to Transactions >… Continue reading Wave
Performance Testing
Performance testing is a type of software testing that evaluates how well a system performs under a specific workload. The objective of performance testing is to identify performance-related bottlenecks and issues in the system and to determine how the system performs under different levels of load. Performance testing can be used to evaluate different aspects… Continue reading Performance Testing
Test Case Documentation- CDUS
Remove Backordered Quantity from Transfer Order The following condition should satisfy for removing backordered quantity from transfer order: The transfer orders status must be any of ‘Pending Fulfillment’ with quantity picked greater than zero, ‘Partially Fulfilled’ and ‘Pending Receipt/Partially Fulfilled’. The quantity entered in custom field should be greater than or equal to the picked… Continue reading Test Case Documentation- CDUS
Remove Backordered Quantity from Transfer Order
In transfer order, if an item line is picked, then its quantity cannot be changed. For example, if the quantity of an item is 20, but only 12 are available, so there will be 8 quantities back ordered. If at least 1 quantity of this item line is picked, then we cannot change the quantity.… Continue reading Remove Backordered Quantity from Transfer Order
Smoke Testing v/s Sanity Testing
Smoke Testing • Smoke testing is the initial testing process exercised to check whether the software under test is ready/stable for further testing. • The Smoke testing is typically executed by testers after every build is received for checking the build is in testable condition. • These test cases are executed prior to start actual testing to check critical functionalities of the program is working fine. • Smoke testing follows shallow and wide approach where you cover all the basic functionality of the software. • The test cases can be executed manually or automated; this depends upon the project requirements. • Smoke Testing, also known as “Build Verification Testing”. Sanity Testing • Sanity testing to check the after minor fixes the small section of code or functionality is working as expected & not breaking related functionality. • The main aim of Sanity testing to check the planned functionality is working as expected. • Sanity testing follows narrow and… Continue reading Smoke Testing v/s Sanity Testing
The sales order is saved, or an alert message appears: Prior to submitting the sales order, the customer record is updated.
Task: If the “Trade partner” field of the salesperson in the sales order record is checked and the currently selected customer’s “trade partner” is also checked, then the sales type will be “Builder Order.” If the checkbox is unchecked, we cannot select “builder order” in a sales order. During the testing of this task, a… Continue reading The sales order is saved, or an alert message appears: Prior to submitting the sales order, the customer record is updated.
The total amount showing in the Sales order and the amount in GL impact of Customer deposit are different
When a Sales order is created the total amount showing in the sales order and the amount showing in GL impact of customer deposit created for the order are different. For Example: Check the screenshot of created sales order and GL impact of customer deposit given below: Sales order: GL impact: Reason for the difference… Continue reading The total amount showing in the Sales order and the amount in GL impact of Customer deposit are different