Author: Agnel Anjuluse

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

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 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

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 • 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