Professional Documents
Culture Documents
Theory
Theory
String - stores text, such as "Hello". String values are surrounded by double quotes
int - stores integers (whole numbers), without decimals, such as 123 or -123
float - stores floating point numbers, with decimals, such as 19.99 or -19.99
char - stores single characters, such as 'a' or 'B'. Char values are surrounded by single quotes
boolean - stores values with two states: true or false.
Object-oriented programming
is a programming paradigm where everything is represented as an object.
Non-functional testing:
Black Box Testing is a software testing method in which the internal structure/ design/ implementation of the
item being tested is not known to the tester
White Box Testing is a software testing method in which the internal structure/ design/ implementation of the
item being tested is known to the tester.
Black box testing: A. Functional Testing ;B. Non-functional testing ;C. Regression Testing
White box testing: A. Path Testing ;B. Loop Testing ;C. Condition testing
Automation Testing or Test Automation is a software testing technique that performs using special automated testing
software tools to execute a test case suite. On the contrary, Manual Testing is performed by a human sitting in front of a
computer carefully executing the test steps. An automated testing tool is able to playback pre-recorded and predefined
actions, compare the results to the expected behavior and report the success or failure of these manual tests to a test
engineer. Once automated tests are created they can easily be repeated and they can be extended to perform tasks
impossible with manual testing. Dynamic Testing is a software testing method used to test the dynamic behaviour of
software code. The main purpose of dynamic testing is to test software behaviour with dynamic variables or variables
which are not constant and finding weak areas in software runtime environment. Static Testing is a software testing
technique which is used to check defects in software application without executing the code. Static testing is done to avoid
errors at an early stage of development as it is easier to identify the errors and solve the errors. It also helps finding errors
that may not be found by Dynamic Testing. REGRESSION TESTING is defined as a type of software testing to confirm
that a recent program or code change has not adversely affected existing features. Retesting is a process to check
specific test cases that are found with bug/s in the final execution. Generally, testers find these bugs while testing the
software application and assign it to the developers to fix it. Then the developers fix the bug/s and assign it back to the
testers for verification. This continuous process is called Retesting. To understand the fundamental test process better,
we can categorize them in the following ways
EXPLORATORY TESTING is a type of software testing where Test cases are not created in advance but testers check
system on the fly. They may note down ideas about what to test before test execution. The focus of exploratory testing is
more on testing as a "thinking" activity. A TEST CASE is a set of actions executed to verify a particular feature or
functionality of your software application. A Test Case contains test steps, test data, precondition, postcondition
developed for specific test scenario to verify any requirement. The test case includes specific variables or conditions,
using which a testing engineer can compare expected and actual results to determine whether a software product is
functioning as per the requirements of the customer. Test suite is a container that has a set of tests which helps testers
in executing and reporting the test execution status. It can take any of the three states namely Active, In progress and
completed. A Test case can be added to multiple test suites and test plans. After creating a test plan, test suites are
created which in turn can have any number of tests. The Bug is the informal name of defects, which means that software
or application is not working as per the requirement. In software testing, a software bug can also be issue, error, fault, or
failure. The bug occurred when developers made any mistake or error while developing the product.
A Bug Report in Software Testing is a detailed document about bugs found in the software application. Bug
report contains each detail about bugs like description, date when bug was found, name of tester who found it, name of
developer who fixed it, etc.
The Responsive design test means testing the website or URL from different devices. Other browsers like Chrome
provide software or program called “Emulator” which will help change the screen features and environment as per the
desired device needed for testing.
Bug Severity or Defect Severity in testing is impact of a bug or a Defect has on the software application under
test. A higher effect of bug/defect on system functionality will lead to a higher severity level. A Quality Assurance engineer
usually determines the severity level of a bug/defect. Priority is defined as the order in which a defect should be fixed.
Higher the priority the sooner the defect should be resolved. Defects that leave the software system unusable are given
higher priority over defects that cause a small functionality of the software to fail.
A mistake in coding is called Error, error found by tester is called Defect, defect accepted by
development team then it is called Bug, build does not meet the requirements then it Is Failure.”