Software Quality - PROG8440

Assignment 2: Determining Levels of Testing and Types for every level

for KNIME.
KNIME Analytics is an open-source analytics platform for creating data science and commercial KNIME
Server for productionizing data science.

Below are the testing levels, methodologies & types with the logical reasons that KNIME Analytics can
use for Testing.

Level Testing Description of Testing Level Type of Test Reason for

No Levels Test Selection
1 Unit Test  The smallest part of the According to the Unit test is the
software is the unit, and requirements, minor most
unit testing means testing Automatic Type is level test, and
the software by dividing it recommended as it because of this,
into minor parts and requires less significant bugs
ensuring that all the units workforce than in the
are working fine without Manual Testing. production can
any bugs. A developer can be avoided,
 All the functions and writes the script and and enormous
particles are rigorously executes it as many time and
tested. times as required and money could
 As we have access to the be sure that the Units be saved at the
codes, it is resolved are working fine. time of
simultaneously if the production.
tester finds any bugs. It also saves
 For Eg: in a calculator, debugging time
testing x+y and x-y all in other testing
separately. levels.
2 Integration  The testing level where In this system, Integration
Test multiple small modules or Automation testing testing detects
parts or functions are can be selected. A the bugs at a
mixed and tested together developer can very early
is integration testing. provide multiple stage, and it is
 Integration testing has input data and test N easier to fix the
different approaches for number of times until detected bugs
testing the modules. and unless the in each
 The approaches are, module is perfect or module.
Incremental, Top-Bottom, breaks.
Bottom-Up, Sandwich & Both the positive and
Big-bang. negative input data
 The Sandwich testing will can be provided, so
be recommended for this the modules are
system as it tests the top- tested.
level modules with the
bottom-level modules
together.
 E.g., In a calculator testing
(x+y)/z*p
3 System  This test is done on the From the diverse System tests
Test complete integrated tests available in the help us to test
system to analyze the system testing below that the
compliance and are the some selected software is
performance of the for KNIME working
system. Performance Test: correctly and
 It tests the system for the It tests the speed, accordingly as
functional requirements scalability, and overall it is defined. It
and system requirements. performance of the specifies how
 The system test is carried system. KNIME the software
out by an independent installs in the system, should behave
team different from the so this test is a must so that there is
development team. as the device should no unwanted
 Different inputs are used not be affected by misbehavior
by the testing tea, software installation. from the
including positive and Regression Test: software in
negative inputs, and the A regression test is production
output is compared to the performed to ensure mode.
interpreted output. that the original
working should not
be affected if any
updates are
performed in the
software.
Functional Testing:
In this test, the tester
lists vital functions
required in the
system and checks for
any missing functions
in the system.
4 Acceptanc  The acceptance test's main The types of Before the
e Test intention is to check Acceptance testing launch, the
whether we build the recommended for acceptance
system right that the user this software are: test is carried
requires. Meaning the Business Acceptance out to check
system is occupied by all Testing (BAT): that the system
the needs of the users. It is concerned with meets the
 This test imitates the meeting the business
business processes and requirements of requirements
tests the software business in the and the
accordingly. scenarios of the customers are
 If that passes, it is business. satisfied with
provided to the customer The business the software
for their Testing and processes are and accept that
finalizing before launching mimicked In the test their
the software. case and tested. requirements
User Acceptance and needs are
 Testing (UAT): fulfilled.
The user, clients and It also
customers conduct determines the
this test to ensure system's
that the system readiness and
correctly satisfies helps solve any
their requirements last-minute
and needs before bugs before
launching. the launch, so
the end-users
do not
complain.

So, according to the above analysis, KNIME should use the four testing levels with defined approaches
and types. A logical reason is also present for selecting the testing methods.

Thanks & Regards,

Yours Worker.