Join date: Feb 23, 2022

Engineering Homework Help: Preparatory Datas

As you would have gathered from the above the process of stuffing the test case to convert it into a test transaction encompasses the following:

1. Master Data Preparation

According to homework help online exoerts there is a lot of spadework to be done very specifically about the building up the master data so that the transactions could be entered smoothly as per expectations. For example, before you open a fixed deposit account of Mr. and Mrs. Shah, you presumably need to:

(i) Allot some Customer ID to them.

(ii) Open their savings bank account.

(iii) Open the account of their introducer.

2. Parameter settings

Almost all the software products provide for user parameters and the right values have to be set against all such parameters. As the software changes its behaviour – marginally though – as per these parameters, you need to take care of all such settings such as interest on savings bank account to be set at say 3.5% holidays to be marked in the calendar, etc.

3. Data span

Perhaps the most grueling task is defining the time span for testing. Like any other project, the testing exercise has to start end on some pre-determined dates, but here we are not talking about that time span. The point of discussion is the dates and time span in the data. It would mean the opening of a fixed deposit account raising a loan and closure of the term deposit account before maturity on some following dates.

According to study daddy all such dates across hundreds of test transactions have to fall within a pre thought and pre-set moderate time span. In other words, you will have to decide that all dates in test data must fall in the range of, say, 01.04.2004 to 31.03.2005. This has to be decided in advance and communicated to all the test team members so that the dates do not go awry reflecting on the efforts of testing.

What is true about dates in the testing of a financial application would also hold good for hours and minutes for testing of an online system and for seconds and milliseconds for testing of real time applications.

4. Common threads of entitles like accounts and manufactured parts

As testing is a real life commercial activity consuming the scarce resources, it has to be intelligently optimized. Towards that, the master data creation could be considered as an overhead and kept to minimum by sharing the master data for as many transactions as possible. Unless special care is taken for this, each tester may design his own individual master data adding to an avoidable burden of stage setting.

Expected results

You have to think and decide about the expected results. Actual testing has to be fast process and your project implementation deadlines will force you to do so. Therefore, according to studydaddy during the actual test process, you can’t afford the redundant time wastage calculating the expected results for counter-checking the correctness of software.

Consider the following examples that clarify the need for keeping the expected results handy:

(i) In the banking application that we have seen, the interest calculations on the deposit as well as advance would be a complex, calculation, especially when it comes to compute the daily products and the penalty reduction in interest rate based on the days the deposit actually was with the bank. An added intricacy in a financial application is to calculate all the sprinkle effects of any transactions on multiple dimensions such as daybook on the time line. General ledger on the dimension of aggregation of accounts etc.

(ii) If you are testing an automation of a product plan, you could appreciate the substantial time and energy needed for exploding the bill of material, where starting with finished goods, you track back its break up in terms of assemblies and sub-assemblies right down to the raw material to figure out the material requirement, plus the time and cost it calls for. It is hence imperative that all the expected results are worked out in advance.

Agility of test data

Lastly, you should also think of the run time modification to test data that may be forced by software errors or some constraints in the environment of the master data set up. If any test transaction has to be deleted or modified, the cascading effects of such a change would again tell on multiple dimensions of time line, aggregation, etc. such a change would again tell on multiple dimensions of time line, aggregation, etc. obviously, one cannot stop, suspend, or re-schedule the testing exercise on that count. It therefore means that the test data (along with the expected results) has to be quite agile to pass the test of real data (along with the expected results) has to be quite agile to pass the test of real life. Test data rigidly recorded in a paper form is discouraged. To ensure such agility of data, it is a common practice that the test data and expected results are maintained on a computer either through general purpose software like a spreadsheet or through another special purpose software product with identical functionality that is well conceived and time tested. Typically, the erstwhile version of the software is the natural choice. Care needs to be however taken that there is no flaw in any computation of the spreadsheet (or the special software, as the case may be), otherwise it may misguide the whole testing exercise.

More resources:

Engineering Homework Help: Program Evaluation Review

Engineering Homework Help: Collective Requirements

Engineering Homework Help: Systems Adequacy, Clarity

Engineering Homework Help: Structured Programming

Engineering Homework Help: Documentation, Sign Off

  • Twitter - White Circle
  • Facebook - White Circle
  • Instagram - White Circle
More actions