Course Project

profiletheman

Fourth Project Deliverable and Set up the user form - Week 6

This is the week that all of the individual application testing for the project is to be completed. Your testing and test results should support the test plan that was created and submitted in Week 4. Although there is no set form for the test results, the results themselves should be based on the desired outcome of the test case as described in the test plan. In the first part of this project discussion, we will explore a couple of possibilities for formatting the test results. The second part of the discussion will address some specific areas that you will need to deal with in setting up your Oracle forms to work correctly within the Citrix environment that you are using.

What Should Test Results Show?

Back to Top

In Week 4, each development team submitted a test plan that outlined what needed to be tested (based on the analysis of the project) and what the expected outcomes or results of each test should be. This test plan is meant to act as the guideline, or blueprint if you will, for the testing that should be under way this week.

In short order, the test results that are offered at the end of the week should support what was stated to be the expected results of the specific test on the test plan. When formulating the test results and thinking through how to present them, it is important to keep in mind that the person looking at the test results should be able to tie each test result back to a specific test case. The next section will present some suggestions on how to tie the test case and the test result together.

Linking the Test Case to the Test Result

Back to Top

One of the key things to consider when trying to determine how to put the test results from the application testing into a presentation format is that it is essential to be able to tie the test case and related test result together. This process can be done in several ways and the following suggestions are meant to offer a starting point. Keep in mind that different areas of the testing will provide different possibilities for formatting or presenting the test results.

Testing the Validation in the XML_PROC and SEQ_PROC - It is conceivable that you could, within one input file containing two records, hit all of the test cases for a particular procedure. If the input record is constructed correctly, then the reference ID for the error message in the procedure would show up in the ERROR_AUDIT table in sequential order. By setting up a script file similar to the one used in Lab 2 to execute the procedure you would be able to show a before look of the ERROR_AUDIT table with no data in it, execute the procedure using the file you have set up with the test data, and then query the table again to see the error entries. You can use the data files provided for Lab 2 as a starting point to create your test files (or the ones provided in Lab 4 and Lab 5). The testing of these three procedures will require the most work.

Testing the INV_UPDATE program - This is another area that you can use the database to provide verification that your application works and is doing what it should. By taking a "before" screen shot of the ITEM table, running your C# application and then taking an "after" screen shot of the table you should be able to verify that the targeted records were updated. Again you have test data from Lab 3 to work with, and have already gone through this process in that lab.

Testing all of the other applications - Taking into consideration what your test cases state, most everything else involves verifying that the application processes a record correctly, reads a record in a file correctly, or writes data to a file correctly. Providing both the input and output file, and somehow showing that the data on the input file is also on the output file should be suitable to satisfy most test cases in this area.

If you have any questions as to how to test a specific area, or satisfy the requirements of a certain test case then you should consult your instructor for suggestions and/or direction. This is one area that is really dependent on what was originally stated in the test plan.

What to Turn in for the Project

Back to Top

There is not a stated format for documenting the test results. This is by design and is left open to see how creative each project team can be. You will not be graded on format, however you will be graded on whether or not you tested what you defined as test cases in the test plan. You should make every effort to tie each test case to a specific test result, and it is also important to show the data that was used for testing. You have been given several example files to use for labs at this point and these might be a good place to start in determining what test data will be needed to satisfy your test plan test cases.

Gather all of your test results, test data and test plan into a single ZIP file and submit it to the project Dropbox for Week 6. Remember also that the Project Team Responsibilities document must be filled out by the development team lead and submitted. This document should outline what each team member did to contribute to the completion of the deliverable. Omission of a team member from this document will result in a possible zero-grade for the assignment. Please be accurate and honest when detailing what the contributions of the team members were.

The User Interface

Back to Top

As has been stated earlier, you are being given a completely functional form to work within the project. There will, however, be a couple of file paths that you will need to alter so that your files will end up in the correct place. You will be given more information on this in the lab for this week. The following diagram shows how the user interface form will look:

Entering Data

Back to Top

The form provided has been set up to help minimize the amount of incorrect data that could be entered. At this point it might be helpful to actually look at how the data in the form will look with data in it. The following diagram shows the user interface form with data entered. The call-out boxes have been added to help point out some of the particular things that you will want to be aware of when working with the form.

There are several things that might be worth pointing out at this time. First, the form itself will not allow the following:

    • Customer ID cannot be blank and must be greater than zero but will not accept more than 6 numbers
    • None of the fields on the form will allow a blank entry
    • The Customer Phone field has a suggested entry format but there is no format mask for this so it is possible to enter a different format
    • The two date fields are masked to accept the date in the shown format
    • Both the Item ID and Quantity drop down fields will allow you to pick the data that you want
    • Each time you add an item it will place the required data in the list box. There is not a limit to the number of items that can be in an order
    • The Place Order button must be pressed to save a customer's order. You will be prompted to select whether or not you wish to place another order for the current customer (see below). If you select Yes, then the current order data will be written to the order and order line files, the order part of the form will clear and you can begin to enter another order starting with the Purchase Date field.

    • If the No button is selected then you will be prompted whether or not you want to place an order for a new customer (see below). If you select Yes then the current data will clear from the form and you can begin with a new customer.

    • If the No button is selected then you will be prompted that the order process is completed and then when the Ok button is selected the form will close and the customer data will be written to the XML file.

The Lab for this week will take you further through the setting up of and use of the form.

Note: If you just close the application window, the appropriate customer and order information may not be written to the files. Be sure to exit the program only after completing an order and declining to create a new customer and order.

    • 10 years ago
    • 20
    Answer(1)

    Purchase the answer to view it

    blurred-text
    Bids(0)