Skip to content

Commit

Permalink
FRESH-258 starting to play with jekyll
Browse files Browse the repository at this point in the history
moving daniela's documentation to tests folder
  • Loading branch information
metas-ts committed May 12, 2016
1 parent 2e5bfcd commit f1be2c8
Show file tree
Hide file tree
Showing 15 changed files with 327 additions and 2 deletions.
1 change: 1 addition & 0 deletions _site/tests/README.md
@@ -0,0 +1 @@
# test-documentation
File renamed without changes.
File renamed without changes.
43 changes: 43 additions & 0 deletions _site/tests/Testcase_FRESH-265.html
@@ -0,0 +1,43 @@
<h1 id="it-fresh-265">IT FRESH-265</h1>
<p>### Procurement Candidates: Packvorschrift overwrite
&gt; Testcase to check if the newly introduced Packvorschrift (M_HU_PI_Item_Product) overwrite set in Betelldisposition (PMM_PurchaseCandidate)
&gt; is also set in orderlines of the corresponding Bestellung.</p>

<ol>
<li>Have a bpartner with a C_Flatrate_Term for procurement, for a product which has different PIs (M_HU_PI_Item_Product) available</li>
<li>Open WebUI for that bpartner, and create a PMM_PurchaseCandidate for that product
<ul>
<li>=&gt; Packvorschrift (M_HU_PI_Item_Product) is the one set in the C_Flatrate_Term</li>
</ul>
</li>
<li>Open Bestelldisposition (PMM_PurchaseCandidate), search for the PMM_PurchaseCandidate you created
<ul>
<li>=&gt; new field Packvorschrift-Produkt Zuordnung abw. (M_HU_PI_Item_Product overwrite)</li>
</ul>
</li>
<li>Set a different Packvorschrift in the new field, save</li>
<li>In Quantity to Order (TU), set any qty you want, save</li>
<li>Press Bestellen in Aktion, OK
<ul>
<li>=&gt; Bestellung for your PMM_PurchaseCandidate is created</li>
</ul>
</li>
<li>Open the Bestellung that was created, print Jasper
<ul>
<li>=&gt; Packvorschrift is the one you set in M_HU_PI_Item_Product overwrite, NOT the one from C_Flatrate_Term / in WebUI</li>
<li>=&gt; Menge TU in orderline = the one you set in PMM_PurchaseCandidate</li>
<li>=&gt; Menge in orderline = qty TU you set in PMM_PurchaseCandidate X qty CU in your Packvorschrift, e.g. 2 TUs X G1x6kg: Menge = 12</li>
<li>=&gt; Packvorschrift displayed in the Jasper is also the one you set in M_HU_PI_Item_Product overwrite</li>
</ul>
</li>
<li>Open Wareneingang POS, search for your orderline
<ul>
<li>=&gt; Packvorschrift-Produkt Zuordnung is the one you set in M_HU_PI_Item_Product overwrite</li>
</ul>
</li>
<li>Select the orderline, OK
<ul>
<li>=&gt; window Quantity to use opens with: Packvorschrift you set in M_HU_PI_Item_Product overwrite selected, the one from C_Flatrate_Term / in WebUI is also selectable</li>
</ul>
</li>
</ol>
File renamed without changes.
File renamed without changes.
File renamed without changes.
7 changes: 7 additions & 0 deletions _windows/C_Order_Purchase.md
@@ -0,0 +1,7 @@
---
mf-InternalName: C_Order_Purchase
mf-Language: de
mf-DisplayName: Bestellung
---

Anderer Test-Fenster-Name
7 changes: 7 additions & 0 deletions _windows/C_Order_Sales.md
@@ -0,0 +1,7 @@
---
mf-InternalName: C_Order_Sales
mf-Language: de
mf-DisplayName: Auftrag
---

Test-Fenster-Name
17 changes: 17 additions & 0 deletions tests/Testcase_01.md
@@ -0,0 +1,17 @@
# Testcase 1
(taken from https://docs.google.com/spreadsheets/d/1kzJpnT0MoAl9XlpSevm1AnAt2i0IDU3D3rBiswtcoYA/edit#gid=0, testcase 11189)
### Procurement: purchase candidates have editable price
> Testcase to check if the price taken from flatrate term / pricelist can be edited in Bestelldisposition after the ProductSupply from WebUI and is correctly taken from there in purchase order, invoice etc.
1. Open Bestelldispo, select a purchase candidate
* Preis: taken from Flatrate_DataEntry; if none was set there: Preis is taken from pricelist
* Preis abweichend: can be added manually
2. Set a price in Preis abweichend, save, then do Aktion: Bestellen, OK
* Bestellung is created
* Preis in orderline: as set in Preis abweichend
3. Complete the Bestellung, make an inout in Wareneingang POS
* HU Editor, Wareneingang POS: VPI costprice = as set in Bestelldispo, Preis abweichend
4. Create the invoice for your Bestellung
* price = as set in Bestelldispo, Preis abweichend


49 changes: 49 additions & 0 deletions tests/Testcase_FRESH-203.md
@@ -0,0 +1,49 @@
# IT FRESH-203
### Procurement: Mail in BPartner language, other eMail Address
> Testcase to check if the emails sent from Doc_Outbound (Ausgehende Belege)
> have the correct sender email address and the text is in the correct
> language.
1. In AD_MailBox (EMail Server), check if the Email Server is set up correctly, or set it up manually (=> http://dewiki908/mediawiki/index.php/ADempiere_Test_Mailbox)
* => you should have an EMail and a Registered EMail (with PW) for your EMail-Server (e.g. smtp.metasconsult.de), with SMTP-Anmeldung checked

1. Add two more emails (AD_MailBox), with the same data (you can copy with details!), but set one with Email for purchase (e.g. einkauf@metasconsult.de) and one for sales side (e.g. verkauf@metasconsult.de)

1. In AD_MailConfig (EMail Server Routing), create an entry for purchase side:
* process: Auswahl als Email an Geschäftspartner senden
* Document BaseType: Purchase Order (Bestellung)
* Doc Sub Type: leave empty
* Mail Box: select the one which includes einkauf@metasconsult.de

1. Create another entry for sales side:
* process: Auswahl als Email an Geschäftspartner senden
* Document BaseType: Sales Order (Auftrag)
* Doc Sub Type: Standard Order (Standardauftrag)
* Mail Box: select the one which includes verkauf@metasconsult.de

1. To make sure you receive the emails yourself, check http://dewiki908/mediawiki/index.php/ADempiere_Test_Mailbox again and set your own email address as the debugmail

1. Select a bpartner that is vendor and customer, and has language = DE set

1. Check the users of this bpartner in tab AD_User, and set your own email address for them

1. Create an Auftrag and a Bestellung for this bpartner

1. Open C_Doc_Outbound_Log (Ausgehende Belege), search for your bpartner and date of test
* => your Auftrag and Bestellung are displayed
1. Press Gear, Auswahl als Email an Geschäftspartner senden

1. Check your email inbox (in Outlook)
* => one email with a confirmation of the Bestellung, with sender address einkauf@metasconsult.de, text & subject in german
* => one email with a confirmation of the Auftrag, with sender address verkauf@metasconsult.de, text & subject in german

1. Go back to bpartner window, and set the language for your bpartner to FR

1. In C_Doc_Outbound_Log (Ausgehende Belege), send emails again with Gear, Auswahl als Email an Geschäftspartner senden for your two orders again

1. Check your email inbox (in Outlook)
* => one email with a confirmation of the Bestellung, with sender address einkauf@metasconsult.de, text & subject in french
* => one email with a confirmation of the Auftrag, with sender address verkauf@metasconsult.de, text & subject in french


4 changes: 2 additions & 2 deletions Testcase_FRESH-265.md → tests/Testcase_FRESH-265.md
@@ -1,9 +1,9 @@
---
what's this: random brainfart wrt metadata
required data
required data:
product: P00001
bpartner: G0007
provided data
provided data:
procurement candidate: 123
---

Expand Down
46 changes: 46 additions & 0 deletions tests/Testcase_FRESH-270.md
@@ -0,0 +1,46 @@
# IT FRESH-270
### material tracking: total received qty and scrap sometimes missing on invoice
> Testcase to check if total received qty and scrap are included in the Endabrechnung
> of a M_Material_Tracking, where the quality inspection (M_QualityInsp_LagerKonf) does not include
> AdditionalFee and ProcessingFee.
1. Find a bpartner that has a C_Flatrate_Term for product P000167_Knollensellerie Lager
1. Create M_Material_Tracking for this bpartner and P000167_Knollensellerie Lager, with correct M_QualityInsp_LagerKonf_Version
1. Create a purchase order for your bpartner, P000167_Knollensellerie Lager, e.g. 15 TUs
1. In orderline, ASI, choose the Material-Vorgang-ID you set in M_Material_Tracking; save & complete
1. In Wareneingang POS, set destination warehouse: Produktion LG for your orderline
1. Make inout for 4 Paloxen
1. Set a different destination warehouse, make inout for the rest
1. Create a PP_Order:
* Type: Waschprobe
* your Material-Vorgang-ID
* product: P000164_Knollensellerie gewaschen
* Workflow: LG Karotten
* BOM: P000164_Knollensellerie gewaschen
* Ressource & Warehouse: Industriestrasse, Produktion LG
* Qty: 500
* Dates: date of test
1. Save & complete
1. Open Produktion Fertigstellung POS, Produktion LG, and select you PP_Order
1. Press Zuteilung, select 2 of your TUs from inout, step 6.
1. Press Empfang, and do receipt for P000164_Knollensellerie gewaschen and P001926_Knollensellerie gross gewaschen
1. Close PP_Order
* => invoice candidates are created for the first PP_Order
1. Open Rechnungsdispo, search for your Material-Vorgang-ID
* => invoice candidates for purchase order and PP_Order:
* => ICs for P000167_Knollensellerie Lager, Paloxe, P000164_Knollensellerie gewaschen and P001926_Knollensellerie
* => IC for MT_Witholding_Akonto_Akonto (Einbehalt)
1. Gear, Fakturierung: invoice the ICs to get the Akonto invoice
* => invoice: Akontozahlung, with P000164_Knollensellerie gewaschen and P001926_Knollensellerie & MT_Witholding_Akonto_Akonto (Einbehalt)
* => jasper for Akontozahlung: displays PP_Order and P000167_Knollensellerie Lager with qty from inout, step 6., and Erdbesatz with resp. qties from 1. PP_Order, 50% Einbehalt
* => invoice: Eingangsrechnung for Paloxen
1. Repeat 8.-15., for the Endabrechnung
* => invoice candidates for PP_Order, as in 14.1, plus IC for MT_Witholding_Akonto_Akonto (Einbehalt)
* => additional IC for MT_RegularPPOrder_Produkt für Auslagerung
* => invoice: Endabrechnung, with P000164_Knollensellerie gewaschen and P001926_Knollensellerie & MT_Witholding_Akonto_Akonto (Einbehalt)
* => jasper for Endabrechnung:
* => displays PP_Orders and P000167_Knollensellerie Lager with qty from inout, step 6., and Erdbesatz with resp. qties from 2. PP_Order
* => Akonto-Netto: net sum from 15.



75 changes: 75 additions & 0 deletions tests/Testcase_FRESH-272.md
@@ -0,0 +1,75 @@
# IT FRESH-272
### hubalance general flatrate filter
> Testcase to check if the filter for flatrate term (= Gebindevertrag)
> is working correctly for hubalance report (Gebindesaldo Gesamt).
1. Have a bpartner with an active flatrate term for HUs, e.g. LU, in C_Flatrate_Term
1. Check the start date & end date for this flatrate term
1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date covered by the period of the flatrate term
* Gebinde Vertrag: Y
* Details anzeigen checked
* => report shows only HUs of the flatrate term with inouts from that period you set in start and end date, with Saldo at start & end date and the inout lines with date and inout no.

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date covered by the period of the flatrate term
* Gebinde Vertrag: N
* Details anzeigen checked
* => report shows HUs NOT covered by the flatrate term with inouts from that period you set in start and end date, with Saldo at start & end date and the inout lines with date and inout no.

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date covered by the period of the flatrate term
* Gebinde Vertrag: null
* Details anzeigen checked
* => report shows all HUs from the two reports before, with Saldo at start & end date and the inout lines with date and inout no.

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date NOT covered by the period of the flatrate term (before or after)
* Gebinde Vertrag: Y
* Details anzeigen checked
* => report is empty

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date NOT covered by the period of the flatrate term (before or after)
* Gebinde Vertrag: N
* Details anzeigen checked
* => report shows all HUs with inouts from that period you set in start and end date, with Saldo at start & end date and the inout lines with date and inout no.

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date NOT covered by the period of the flatrate term (before or after)
* Gebinde Vertrag: null
* Details anzeigen checked
* => report shows all HUs with inouts from that period you set in start and end date, with Saldo at start & end date and the inout lines with date and inout no.

1. Run Gebindesaldo Gesamt for your bpartner with:
* start date BEFORE the start date of the flatrate term, and end date covered by the period of the flatrate term
* Gebinde Vertrag: Y
* Details anzeigen checked
* => report shows only HUs of the flatrate term with inouts from the WHOLE period you set in start and end date, with Saldo at start & end date and the inout lines with date and inout no.

1. Add another flatrate term for your bpartner for another type of HUs, e.g. IFCO 6014, in C_Flatrate_Term
1. Set start date & end date, BUT don't commplete it
1. Make an inout for the HU of your new flatrate term, e.g. with Leergutausgabe

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date covered by the period of the new flatrate term
* Gebinde Vertrag: Y
* Details anzeigen checked
* => report is empty OR does not include inouts for the HU of the new flatrate term, but only the HU of the old one

1. Complete the new flatrate term

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date covered by the period of the new flatrate term
* Gebinde Vertrag: Y
* Details anzeigen checked
* => report shows the new HU with the inout you created earlier, with Saldo at start & end date and the other inout lines with date and inout no. (if they exist), and the HU of the old flatrate term

1. Go back to your inout you created before, reactivate it

1. Run Gebindesaldo Gesamt for your bpartner with:
* start & end date covered by the period of the new flatrate term
* Gebinde Vertrag: Y
* Details anzeigen checked
* => report is empty OR does not include the inout for the HU you reactivated, but only different inouts of that HU type or the inouts for the HU of the old flatrate term
80 changes: 80 additions & 0 deletions tests/Testcase_FRESH-272_version_2.0.md
@@ -0,0 +1,80 @@
# IT FRESH-272
### hubalance general flatrate filter
> Testcase to check if the filter for flatrate term (= Gebindevertrag)
> is working correctly for hubalance report (Gebindesaldo Gesamt).
Setup for test (dates are examples, can be changed accordingly!):
* bpartner X with active flatrate term I in C_Flatrate_Term for Gebinde, e.g. LU A
* start date of flatrate term I: 01.05.16
* end date of flatrate term I: 30.06.16
* several inouts for LU A and other types of HUs (e.g. IFCO C, Paloxe) from time period 01.05. - 30.06.16


| Gebindesaldo Gesamt Filters | Results displayed in Jasper Report |
| ----------------------------- |:-------------------------------------------------------------:|
| start date 01.05.16 | Saldo on 01.05.16 |
| end date 15.06.16 | Saldo on 15.06.16 |
| Geschäftspartner X | results for bpartner X only |
| Gebinde Vertrag Ja | results for LU A only, no other type of HU included |
| Details anzeigen checked | inout lines from 01.05. - 15.06.16 with date and inout no. |



| Gebindesaldo Gesamt Filters | Results displayed in Jasper Report |
| ----------------------------- |:-------------------------------------------------------------:|
| start date 01.05.16 | Saldo on 01.05.16 |
| end date 15.06.16 | Saldo on 15.06.16 |
| Geschäftspartner X | results for bpartner X only |
| Gebinde Vertrag Nein | results for other types of HU, LU A NOT included |
| Details anzeigen checked | inout lines from 01.05. - 15.06.16 with date and inout no. |



| Gebindesaldo Gesamt Filters | Results displayed in Jasper Report |
| ----------------------------- |:-------------------------------------------------------------:|
| start date 01.05.16 | Saldo on 01.05.16 |
| end date 15.06.16 | Saldo on 15.06.16 |
| Geschäftspartner X | results for bpartner X only |
| Gebinde Vertrag Null | results for all types of HU, LU A included |
| Details anzeigen checked | inout lines from 01.05. - 15.06.16 with date and inout no. |



| Gebindesaldo Gesamt Filters | Results displayed in Jasper Report |
| ----------------------------- |:-------------------------------------------------------------:|
| start date 01.04.16 | report is empty |
| end date 30.04.16 | |
| Geschäftspartner X | |
| Gebinde Vertrag Ja | |
| Details anzeigen checked | |



| Gebindesaldo Gesamt Filters | Results displayed in Jasper Report |
| ----------------------------- |:-------------------------------------------------------------:|
| start date 01.04.16 | Saldo on 01.04.16 |
| end date 30.04.16 | Saldo on 30.04.16 |
| Geschäftspartner X | results for bpartner X only |
| Gebinde Vertrag Nein | results for all types of HU, LU A included |
| Details anzeigen checked | inout lines from 01.04. - 30.04.16 with date and inout no. |

| Gebindesaldo Gesamt Filters | Results displayed in Jasper Report |
| ----------------------------- |:-------------------------------------------------------------:|
| start date 01.07.16 | Saldo on 01.07.16 |
| end date 30.09.16 | Saldo on 30.09.16 |
| Geschäftspartner X | results for bpartner X only |
| Gebinde Vertrag Null | results for all types of HU, LU A included |
| Details anzeigen checked | inout lines from 01.07 - 30.09.16 with date and inout no. |

| Gebindesaldo Gesamt Filters | Results displayed in Jasper Report |
| ----------------------------- |:-------------------------------------------------------------:|
| start date 01.04.16 | Saldo on 01.04.16 |
| end date 30.05.16 | Saldo on 30.05.16 |
| Geschäftspartner X | results for bpartner X only |
| Gebinde Vertrag Ja | results for LU A only, no other type of HU included |
| Details anzeigen checked | inout lines from 01.04 - 30.05.16 with date and inout no. |

0 comments on commit f1be2c8

Please sign in to comment.