QA test plan 2.40/Save on button
Contents |
Introduction
Currently it is necessary to save a record before the execution of any process on it, for example when pressing the button complete in Sales Order window
Aim of the project
The goal of this project is to add the ability of saving automatically the current record when a button is clicked, this would prevent the "do you want to save?" message if the button is clicked but the record was not previously saved This project affects all the automatically generated windows that include at least one button
Test cases
When buttons are configured as save button
- Previous configuration:
- Additional data: By default the buttons are configured as autosave so you can skip this step
- Login into English with System administrator role
- Go to Application dictionary->Window&tabs and fields and for all the windows below go to the header tab and configure the field "Auto Save" as Yes marking the flag
- Go to the console and being in the home folder of the project and compile:
- ant compile -Dtr=no
- ant war
- deploy the war file in the webapps tomcat folder
1. Sales order window
- Steps:
- Login as Openbravo with role that access to the Sales Order Window
- Go to Sales management Window->Sales order->Header
- Click New and fill the mandatory fields
- Before save the new record click the button "Copy lines"
- Issues to verify: The button should show correctly and after selecting one or more lines the selected lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Click New and fill the mandatory fields
- Before save the new record click the button "Copy from order"
- Issues to verify: The button should be showed correctly and after selecting the order and clicking OK one or more lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Click New and fill the mandatory fields. Save
- Move to the lines tab and create one line filling the mandatory fields. Save
- Move back to the header and fill the field Order Reference and click the button "Complete"
- Issues to verify:
- The button should be showed correctly and after selecting the action complete and clicking OK everything should go well.
- No messages alerting the record has been changed should appear. In order to make this happen, first the header should have been saved by clicking the button
2. Goods receipt window
- Steps:
- Login as Openbravo with role that access to the Goods receipt window
- Go to Procurement management Window->Goods receipt->Header
- Click New and fill the mandatory fields
- Before save the new record click the button "Create lines from"
- Issues to verify: The button should show correctly and after selecting one or more lines the selected lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Click New and fill the mandatory fields. Save
- Move to the lines tab and create one line filling the mandatory fields. Save
- Move back to the header and fill the field Order Reference and click the button "Complete"
- Issues to verify:
- The button should be showed correctly and after selecting the action complete and clicking OK everything should go well.
- No messages alerting the record has been changed should appear. In order to make this happen, first the header should have been saved by clicking the button
3. Sales invoice window
- Steps:
- Login as Openbravo with role that access to the Sales Invoice Window
- Go to Sales management Window->Sales Invoice->Header
- Click New and fill the mandatory fields
- Before save the new record click the button "Create lines from"
- Issues to verify: The button should show correctly and after selecting one or more lines the selected lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Click New and fill the mandatory fields
- Before save the new record click the button "Copy lines"
- Issues to verify: The button should be showed correctly and after selecting the invoice and clicking OK one or more lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Click New and fill the mandatory fields. Save
- Move to the lines tab and create one line filling the mandatory fields. Save
- Move back to the header and fill the field Order Reference and click the button "Complete"
- Issues to verify:
- The button should be showed correctly and after selecting the action complete and clicking OK everything should go well.
- No messages alerting the record has been changed should appear. In order to make this happen, first the header should have been saved by clicking the button
4. Settlement window
- Steps:
- Login as Openbravo with role that access to the Settlement Window
- Go to Financial management->Receivables&Payables->Transactions->Settlement->Settlement
- Click New and fill the mandatory fields
- Before save the new record click the button "Create lines from"
- Issues to verify: The button should show correctly and after selecting one or more lines the selected lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Move to the Created Payments tab and created a payment that its amount is the sum of the amount of the payment that are in the Cancelled Payment tab. Don't forget to fill the mandatory fields. Save
- Move back to the header and write something in the field description and click the button "Process"
- Issues to verify:
- The button should be showed correctly and after clicking OK everything should go well.
- No messages alerting the record has been changed should appear. In order to make this happen, first the header should have been saved by clicking the button
5. Bank Statement window
- Steps:
- Login as Openbravo with role that access to the Bank Statement Window
- Go to Financial management->Receivables&Payables->Transactions->Bank Statement->Header
- Click New and fill the mandatory fields
- Before save the new record click the button "Create lines from"
- Issues to verify: The button should show correctly and after selecting one or more lines the selected lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Write something in the field description and click the button "Process"
- Issues to verify:
- The button should be showed correctly and after clicking OK everything should go well.
- No messages alerting the record has been changed should appear. In order to make this happen, first the header should have been saved by clicking the button
6. Gl journal window
- Steps:
- Login as Openbravo with role that access to the Bank Statement Window
- Go to Financial management->Accounting->Transactions->Gl journal->Header
- Click New and fill the mandatory fields
- Before save the new record click the button "Copy details"
- Issues to verify: The button should show correctly and after selecting one or more lines the selected lines should go to the lines tab. In order to make this happen, first the header should have been saved by clicking the button
- Change the field Accounting date and click the button "Process"
- Issues to verify:
- The button should be showed correctly and after clicking OK everything should go well.
- No messages alerting the record has been changed should appear. In order to make this happen, first the header should have been saved by clicking the button
When buttons are configured as not save button
- Previous configuration:
- Additional data: By default the buttons are configured as autosave so you must follow the following preconditions
- Login into English with System administrator role
- Go to Application dictionary->Window&tabs and fields and for all the windows below go to the header tab and configure the field "Auto Save" as No marking the flag. The windows are: Sales order, Goods receipt, Sales invoice, Settlement, Bank Statement, Gl journal
- Go to the console and being in the home folder of the project and compile:
- ant compile -Dtr=no
- ant war
- deploy the war file in the webapps tomcat folder
What the tester has to do is to verify that if you run the above test cases for each of them whenever you click a button a message should show up saying that
Results
All the related bugs will have the prefix QA-SB
One bug reported. Click here to see it
Category: QualityAssurance


