Lesson 2 Flashcards

1
Q

refers to the process of testing any software application using scripts, tools, or any test
automation frameworks in order to identify errors.

A

Application testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

. It helps teams release bug-free and robust software applications into
the real world. It also enables teams to identify bugs in the early stages of development and save development time.

A

Application testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

approach is used more
frequently by developers in the initial phases of the
development for testing specific features.

A

Manual Testing –

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Application testing is carried out in two phases –

A

Frontend or User Interface testing and

Backend testing that verifies the database behavior.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

– Once the software application is entirely
developed, QAs automate test scenarios or test cases from the
end-users’ perspective to evaluate the usability, functionality,
and performance of the application

A

Automated Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

are used to verify that the application functions
as expected under specific conditions.

A

test cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

When a software application is developed, it
goes through various stages of testing. The tests may vary from being
functional to non-functional, subject to test requirements.

A

MANUAL TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

When not create Test Scenario?

Test Scenarios may not be created when:

  1. The Application Under Test is complicated, unstable and there is a time
    crunch in the project.
  2. Projects that follow Agile Methodology like Scrum, Kanban may not create
    Test Scenarios.
  3. Test Scenario may not be created for a new bug fix or Regression Testing. In
    such cases, Test Scenarios must be already heavily documented in the
    previous test cycles. This is especially true for Maintenance projects.
A

TRUE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

are used to verify that an application works
as expected overall.

A

test scenarios

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

consists of multiple test
cases with detailed instructions about how to test specific
end-to-end functionality and user experience

A

test scenario

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

is a vast domain

A

TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

There are two ways for QAs to carry out tests:
1.By manually executing test cases as mentioned in the written test plan
2.By automating test scenarios using frameworks like Selenium WebDriver

A

TRUE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

In a tech-advanced world where automation tools and frameworks are
making life easier for test engineers, it would be normal to assume that
manual testing is obsolete. This, however, is completely untrue.

A

TRUE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Refers to a test process in which a QA manually tests the software application in order to
identify bugs. To do so, QAs follow a written test plan that
describes a set of unique test scenarios. The QA is required to
analyze the performance of the web or mobile application from
an end user’s perspective.

A

MANUAL TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

verify the actual behavior of software against expected
behavior, and any difference is reported as a bug

A

QA

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Involves verification of individual components or units of source code.

A

Unit Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

can be referred to as the smallest testable part of any
application.

A

UNIT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

It focuses on testing the functionality of individual components
within the application. It is often used by developers to discover bugs in
the early stages of the development cycle.

A

UNIT TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

would be as fundamental as clicking a button and
verifying whether it performs the desired operation. For example, ensuring
that a share button lets you share the correct page link

A

UNIT TEST CASE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

is the next step after unit testing.
Multiple units are integrated to be tested as a whole. For
example, testing a series of application interfaces in a particular
order to verify interoperability

A

INTEGRATION TESTING

17
Q

his approach helps QAs evaluate how several components of
the application work together to provide the desired result.
Performing integration testing in parallel with development
allows developers to detect and locate bugs faster.

A

INTEGRATION TESTING

18
Q

involves testing all the
integrated modules of the application as a whole. It helps QAs
verify whether the system meets the desired requirements. It
includes multiple tests like validating output based on specific
input, testing user experience and more.

A

SYSTEM TESTING

19
Q

Teams perform several types of system testing
like regression testing, stress testing, functional testing and
more, depending on their access to time and resources.

A

SYSTEM TESTING

19
Q

to verify whether the system as a whole is fit for use in the real world.

A

ACCEPTANCE TESTING

20
Acceptance testing is performed both internally and externally. Internal acceptance testing (also known as alpha testing) is performed by the members within the organization. External testing (also known as the beta testing) is performed by a limited number of actual end-users. This approach helps teams evaluate how well the product satisfies the user’s standards. It also identifies bugs in the last stage before releasing a product.
true
21
also known as glass box or transparent testing, is an approach in which the QA is familiar with the internal code or structure of the application. It is primarily used for unit testing.
WHITE BOX TESTING
21
also covers specific techniques like data flow testing, control flow testing, decision coverage, and path testing, and a few others
WHITE BOX TESTING
22
is a test approach in which the QA doesn’t have any knowledge about the underlying code or structure of the application.
BLACK BOX TESTING
22
The QA interacts with the software application just like an end-user to test its functional and non-functional behavior. This helps to discover some bugs typically overlooked in the earlier stages.
BLACK BOX TESTING
23
approach is the combination of both white box and black box testing techniques. The main aim of this approach is to identify any bugs present either due to inappropriate usage or any structural flaws.
GREY BOX TESTING
24
Regression suites are ever-increasing, and require the same variables to be filled numerous times to ensure that new features do not tamper with older functions. This can easily be automated.
* Regression Testing
25
Automate all tests requiring complex calculations, something prone to human error.
* Testing of complex functionalities:
26
Run automated suites to verify the quality of major functionalities. This saves time by offering a quick analysis of whether a build requires more in-depth testing.
SMOKE TESTING
27
Tools cannot replicate any user journey in its entirety. It is impossible for an algorithm to predict how individual users will interact with an application. In order to actually judge the quality of user experience, stick to human testers. Try using manual interactive testing tools like BrowserStack Live.
User experience testing:
28
: When testing how accessible an application is, there is no substitute for human usage. A tool cannot measure accessibility because every people often have different opinions on what counts as accessible. It is not possible for a tool to recognize if software workflow is providing easy access for actual humans. * Select the right tools
Accessibility testing
29
is an integral part of any testing ecosystem. Without moving to an automation setup, comprehensive testing becomes difficult, as do the meeting of ever-shortening deadlines.
AUTOMATION TESTING
30
Consequently, it is important to initiate automation testing protocols as early as possible in a way that balances and complements manual testing.
TRUE
31
ensures a high-end User Experience to the end user of the software, as it requires human observation and cognitive abilities.
Manual Testing - User Experience
32
should be used to perform Exploratory Testing, Usability Testing and Adhoc Testing to exhibit the best results.
Manual Testing -Areas of Specialization
33
Users must have the ability to mimic user behavior and build test plans to cover all the scenarios.
Manual Testing -User Skills
34
cannot guarantee a good User Experience since the machine lacks human observation and cognitive abilities.
Automation Testing - User Experience
35
Automation Testing should be used to perform Regression Testing, Load Testing, Performance Testing and Repeated Execution for best results.
Automation Testing -Areas of Specialization
35
Users must be highly skilled at programming and scripting to build test cases and automate as many scenarios as possible.
Automation Testing -User Skills
36
Software applications are mainly categorized into three types: 1.Web-applications 2.Mobile applications (Android, iOS) 3.Desktop applications
TRUE
37
is any program that helps QAs manage and regulate the test process. Deciding which application testing software or framework is to be used varies according to the nature of the application to be tested.
Application testing tool
38
is the most popular tool suite for automating web application testing. It enables QAs to verify the cross browser compatibility of a web-application using Selenium WebDriver
SELENIUM
39
For testing native, web, and hybrid mobile applications,
APPIUM
40