Search results
From Opentaps Wiki
Jump to navigationJump to search
Page title matches
- This test verifies that each of the receiving screens could only receive their own sp786 bytes (115 words) - 22:17, 30 August 2007
Page text matches
- These tests involve both purchasing and warehouse and allow you to test how creating, receiving, and force completing PO can be done: ===Test 1: Create PO and Receive Unapproved PO===1 KB (214 words) - 01:59, 8 December 2007
- ===Test 1: Auto requirement not created when order is first created=== ===Test 2: Auto requirement not created when order is approved===3 KB (426 words) - 18:20, 5 December 2007
- ===Test Receive Non-serialized Inventory Item=== ===Test Receive Serialize Inventory Item===883 bytes (124 words) - 00:24, 16 February 2008
- ===Test 1: Owner of Emails=== ===Test 2: Order ID Processed Correctly===2 KB (336 words) - 23:26, 30 November 2007
- Test cases: ====Test Case 1: Commission for Any Product based on Order/Invoice Role====4 KB (601 words) - 18:30, 24 September 2008
- ===Test Entering Estimated Delivery Dates=== ===Test Updating Delivery Dates===1 KB (231 words) - 02:28, 14 February 2008
- ===Test Receiving a Purchase Order=== ===Test Manufacturing a Product===2 KB (371 words) - 20:02, 29 October 2008
- payment.authorizedotnet.url=https://test.authorize.net/gateway/transact.dll payment.authorizedotnet.test=FALSE3 KB (470 words) - 18:21, 26 August 2010
- Create another sales invoice to DemoCustomer with a reference number "test". Create another sales invoice to DemoCustomer with reference number "test".4 KB (610 words) - 06:07, 21 April 2008
- Also when running unit tests one can chose to run only one test, for example: where -Dtest=<name of the unit test classes (can be comma separated)>5 KB (768 words) - 22:50, 27 January 2012
- ===Test 1. Verify correct product lookup=== ===Test 2. Verify the correct quantities are adjusted for the correct reason.===1 KB (241 words) - 20:29, 18 December 2007
- ...ch month, we can invoice the university for products they have sold. This test will ensure the critical aspects of this system work. ===Test 1: Create Partner===6 KB (850 words) - 01:21, 28 November 2007
- prompt:> mail -s "test subject" someone@somewhere.com This should basically be it. Commit something to test things out. If there is a problem, it will usually show up in the mail ser2 KB (345 words) - 00:40, 27 March 2008
- ||Test 1: Verify Basic MRP ||Test 2: Verify Approved Requirements for MRP7 KB (1,071 words) - 16:19, 11 December 2007
- public * fr.umlv.*.test.*.start*(int, String, *) public void fr..Test.SetParams(..)4 KB (567 words) - 00:52, 21 July 2009
- payment.authorizedotnet.test=TRUE payment.authorizedotnet.test=FALSE10 KB (1,590 words) - 18:49, 22 June 2010
- ===Balance limit test===3 KB (476 words) - 01:11, 13 September 2007
- * Install the Java "SDK" release needed for your test computer, from the Java community software download site. * Login with a test ID and password provided in the release download, and evaluate opentaps in2 KB (271 words) - 14:16, 1 April 2010
- * Install the Java "SDK" release needed for your test computer, from the Java community software download site. * Login with a test ID and password provided, and evaluate opentaps in more detail for your com2 KB (307 words) - 20:38, 30 March 2010
- ...f a product with one internal task followed by two outsourced tasks. This test is a combination of [[Making a Product with One Internal Manufacturing Step2 KB (298 words) - 18:24, 11 March 2009