Marketing: System Test Plan Report for Enterprise System Testing

This report presents a system test plan for a large enterprise company, addressing the architecture provided. The document details the purpose and functional scope of the test plan, focusing on various organizational functions like accounting & finance, sales & marketing, and human resources. It outlines the testing strategy, including methods, objectives, and resource allocation. The report also covers system testing entrance criteria, test data considerations, suspension and resumption criteria, and the execution plan. It further addresses defect reporting mechanisms, test schedules, testing environments, and potential risks, along with assumptions and a 'who-to-call' list for approvals. The plan emphasizes the importance of automation and provides references to relevant literature in the field of software testing and enterprise systems.

Running head: MARKETING
Marketing
Name:
Institution:
Date:

MARKETING
System test plan
Purpose of the document
The purpose of the document is to determine the amount of effort needed in order to validate
the application quality under the test. It helps the people outside the scope of the test team such as
business managers, developers and customers understand the testing details. Teat documentation is
created during or before the software testing. It helps to estimate the effort needed to execute the
progress, test coverage and to check on resource tracking (Considine, et al,2016).. It is a comprehensive
suite of documents that allows the test team to document and describe test planning, design, execution
and the test results drawn from the test activity.
Functional scope
The functional scope will be centered on the functions of the organization including
accounting & finance, sales & marketing, manufacturing & supply and Human resources functions.
All these will then be derived from various processes such as the Sales& Marketing processes,
Accounting & Finance Processes, HR processes, and the Manufacturing & Supply processes. In all
these processes, a central database is made to have all functional systems run through it as the entire
enterprise system.
The process of assessing the conformity of a product with explicit requirements
(specifications) is verification, at the same time, assessing the conformity of a product with the
expectations and requirements of users is validation (Gilman., Fronczyk, & Wilson, 2019). You can also
often find the following definition of these concepts:
Validation - ’is this the right specification?’
Verification - ’is the system correct to specification?’
Testing Strategy

MARKETING
A test strategy for the enterprise describes the software development testing approach and
cycle. The key issues in the testing strategy is to inform the testers of the software, project managers
and developers on key testing process issues. The testing strategy includes; methods of testing the
new functionalities, testing objectives, resources required for testing and time for testing new
functions. The testing strategy will also look at the testing environment. The test strategies in this
system will describe how stakeholder’s risks are mitigated at the level of testing, the types of tests that
are to be performed and the type of entry and exit criteria required. The test strategies are created
basing on the developed document designs (Kothandaraman, et al,2018).
System testing entrance criteria
System testing is putting all the functions in the system to test. All the processes are tested
and components integrated so as to verify if the system is working as planned or not. After integration
testing, system testing is thereafter done. System testing plays an important role in producing a high
quality system or product. System testing criteria are fundamentally used while occasional conceptual
design testing is referred to. Documentation design are used to describe the software functionality to
enable in the upcoming release. For each stage of design development, a corresponding strategic test
is created to test new feature tests.
Test data
In programming or software development of the enterprise, the data that will specifically be
identified for test use is called the test data. In this software testing, some data may be used in
verification of a given input function to produce some expected results. Others are used to verify data
in a complementary way. The accounting and finance department will mostly be used in this test of
data. Other data may be used so that to see if there is an ability of the program to respond in an
unusual, unexpected, exceptional and extreme way. Test data can be produced by the programmer or
the tester or any other function that helps the tester. The test data may be recorded for it to be re-used
or used only once and then forgotten (Modarres, Kaminskiy, & Krivtsov, 2016).

MARKETING
Suspension criteria
The software must be tested before release. As the software industry matures, testing
approaches have matured. Instead of a myriad of living testers, the developers switched to automating
most of the tests. Automation of tests allows you to find out about a bug in seconds and minutes after
it is entered into the code, and not after a few days or weeks. The suspension criteria is used to
suspend part or all portion of the testing activities. Resumption criteria in software testing will
specify when testing should presume after suspension (Smith, 2017)..
Execution plan
Software has become an integral part of the world in which we live. It outgrew the original
sole purpose of increasing business efficiency. Today, every company strives to become a first-class
digital company. Every day we all act as users of more and more software. The speed of innovation is
increasing. Obviously, testing all changes manually takes a lot of time, it is monotonous and tedious.
Monotony is boring, and boredom leads to mistakes. Fortunately, there is a great tool for the same
tasks: automation. Automating uniform tests will change your life as a developer. Automate tests, and
you will no longer have to thoughtlessly follow click protocols, checking the correct operation of the
program. Automate the tests, and without changing your eyes, change the code base. If you've ever
tried large-scale refactoring without the right set of tests, I'm sure you know what horror this can turn
into. How do you know if you accidentally make a mistake in the process? Well, you have to click
manually on all test cases, how else. But let's be honest: do you really like it? How about even after
large-scale changes, any bugs manifest themselves within a few seconds while you are drinking
coffee? In my opinion, this is much nicer.
Defect reporting
In case of defects in the system, the system generates its own mechanisms showing failure or
a defective system. Defective reporting is done to the data base and the tester of the system is notified.
If you take automated tests seriously, there is one key concept: the test pyramid. This is an excellent
visual metaphor, suggesting different levels of tests. It also shows the volume of tests at each level.

MARKETING
Test schedule
Characteristics and schedule of tests depends on many factors that should not be tested.
Designed to preliminarily determine which objects are not subject to testing. This may be specific
functions, the implementation of which is postponed until the release of the next version of the
program, or settings and functions that cannot be tested during the time that is allocated for this
testing (Stamatis, 2017).
Environment
Static and dynamic testing, which should be conducted on stages of testing software modules
and codes. Property testing, load tests, overload tests, performance testing, testing of installation,
updating of software product and means of duplication, recovery, acceptance tests: alpha, beta and
other types of tests in place, use of a defect tracking system.
Risks
The risks in the system test planning include;
 Missing the deadline that is deployed.
 Reduced return on investment( ROI)
 Increased in cost of production
 Software that are poorly designed and of poor quality
 Failure to meet contractual obligations
Assumption
Do not forget about the distribution of responsibility during testing. If the work of your test
group is associated with another group, then it will be advisable to draw up a schedule for the
distribution of test works, in other words, who does what and in what time frame (Virtanen, 2019).
Who-to-call list

MARKETING
If the test plan requires approval or agreement with certain organizations / persons, then this
must be done in a timely manner. It is impossible to violate the terms of testing, the test design must
be carried out according to the established plan, and the work performed must be delivered to the
customer on time (Zou, Holmes, & Shah, 2016,)..

MARKETING
References
Considine, C., Crowley, S., Gardner, G., Shannon, C., Kwinn, M. J., Henderson, S. J., & Santamaria, P. (2016, April).
Architecting a development and testing plan for the Army's common operating environment: Applying agile
systems of systems development to army network acquisition. In 2016 Annual IEEE Systems Conference
(SysCon) (pp. 1-6). IEEE.
Gilman, J. F., Fronczyk, K. M., & Wilson, A. G. (2019). Bayesian modeling and test planning for multiphase reliability
assessment. Quality and Reliability Engineering International, 35(3), 750-760.
Kothandaraman, S. R., Malekpour, A., Maigha, M., Paaso, A., Zamani, A., Katiraei, F., & Lelic, M. (2018, November).
Utility Scale Microgrid Controller Power Hardware-in-the-Loop Testing. In 2018 IEEE Electronic Power Grid
(eGrid) (pp. 1-6). IEEE.
Modarres, M., Kaminskiy, M. P., & Krivtsov, V. (2016). Reliability engineering and risk analysis: a practical guide.
CRC press.
Smith, D. J. (2017). Reliability, maintainability and risk: practical methods for engineers. Butterworth-Heinemann.
Stamatis, D. H. (2017). The OEE primer: understanding overall equipment effectiveness, reliability, and maintainability.
Productivity Press.
Virtanen, V. (2019). STH System Testing-Change Management.
Zou, T., Holmes, J., & Shah, V. (2016, May). BOP System Reliability Planning and Testing. In Offshore Technology
Conference. Offshore Technology Conference.