Task Description A four level approval workflow is created for bill payment.First Level Approval- Clerk accounts payable can create the vendor payment record,Submit for approval button shown to Clerk accounts payable and Administrator.Second Level Approval-The Account payable can view the vendor payment list in the NetSuite dashboard. The Accountant payable and Administrator can view the… Continue reading MAMS 226- Test Case Documentation
Author: Athul N.V
Pair Testing
Pair Testing is a software testing technique in which two testers work together on testing the same software or system. One tester is the driver, and the other is the observer. The driver performs the testing by executing test cases, while the observer watches and takes notes. The testers switch roles frequently to ensure that… Continue reading Pair Testing
SWFT-442 Test Case Documentation
Task Description:Create a Custom record with the name “Sales Rep, Owner Id, Co-Owner History” and add that custom record in the lead records custom subtabAdd the fields Old Owner ID, New Owner ID, Old Sales Rep, New Sales Rep, Old Co-Owner, New Co-Owner, and Updated Date in the custom recordIf a change is made in… Continue reading SWFT-442 Test Case Documentation
Contract acceptance testing
Contract acceptance testing is a process of testing whether a software system meets the requirements specified in a contract or agreement between two parties. This type of testing is usually performed by the customer or client who has entered into a contract with a software development company to build a custom software application. The purpose… Continue reading Contract acceptance testing
Mismatch in Quantity Remaining
The following scenario occurs: Client wants to display the remaining quantity in packing slip. while creating the first Item Fulfillment, the remaining quantity shows correctly. ie, Remaining Qty= Ordered Qty -Shipped Qty. When we create another IF for the same order, the latest remaining Qty is displayed, After that if we check previous packing slip… Continue reading Mismatch in Quantity Remaining
Ad Hoc Testing
Ad Hoc Testing is a software testing technique where the tester performs testing in an unstructured and informal manner without following any predefined test plan or test case. The term “ad hoc” means “for a specific purpose” or “improvised,” and therefore, ad hoc testing is also known as improvisational testing or exploratory testing. Ad hoc… Continue reading Ad Hoc Testing
Cross Browser Testing
Cross-browser testing is the process of testing a software application or website to ensure that it works correctly and appears the same across different web browsers and browser versions. Since different browsers have different rendering engines, features, and quirks, cross-browser testing is essential to ensure that a software application or website is accessible and functional… Continue reading Cross Browser Testing
Boundary Analysis Testing
Boundary analysis is a testing technique used in software engineering to identify and test the boundaries or limits of input parameters. The objective of boundary analysis is to ensure that the software being tested can handle all possible input values, including the highest and lowest possible values, without producing any unexpected results. In boundary analysis,… Continue reading Boundary Analysis Testing
Search to get Child item (Name only)
Using this formula only Child Item Names will displayed in the formula column Criteria :Parent:Name is not empty Result:Name, Formula Text : ltrim(regexp_substr({name},'[^:]*$’))
SMOKE TESTING AND SANITY TESTING
Smoke Testing: Smoke testing is an initial testing done to check if the critical functionalities of the application are working fine. It is a quick and shallow test that aims to identify major issues before proceeding to more comprehensive testing. Smoke testing is usually performed after a new build is released to ensure that the… Continue reading SMOKE TESTING AND SANITY TESTING