Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Test Engineering > Qa Methodology > Flashcards

Qa Methodology Flashcards

1
Q

Unit testing

A

Is the first level of dynamic testing and is the first responsibility of the developers and then the testers.

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

Functional testing

A

Black-box type of testing geared to functional requirements of application.

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

Usability testing

A

Testing for ‘user-friendliness’.
Examples: User interviews, surveys.
Not for devs and testers

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

Integration testing

A

Testing of combined units. Makes sure distinct components of the application still works in accordance to customer requirements

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

System testing

A

Testing of a complete system in a controlled environment.

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

End-to-End testing

A

Testing of a complete application environment in a situation that mimics real-world use.

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

Regression testing

A
  • verify new features
  • bugs in the new feature
  • the new feature did not brake any existing code
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Sanity testing

A

Sanity Testing is done to check the new functionality/bugs have been fixed. It exercises only the particular component of the entire system.
It is a subset of regression testing.

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

Smoke testing

A

Is performed to ascertain that the critical functionalities of the program is working fine. It exercises the entire system from end to end.
Subset of acceptance testing.

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

Performance testing

A

Will verify the load, volume and response times as defined by requirements.
Part of non-functional testing.

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

Load testing

A

Testing application under heavy load and determine at what point the system response time degrades or fails.
Type of non-functional testing.

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

Compatibility testing

A

To measure how well software performs in a particular hw/sw/operating/network environment

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

Acceptance testing

A

Done by the client to verify the system functionality and usability prior to the system moved to prod. Testers work with the client to develop acceptance criteria

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

A/B testing

A

is a user experience research methodology that compares multiple versions of a single variable to determine which is more effective

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

Non-functional testing

A

is defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application

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

Test strategy

A

Is a set of instructions or protocols which explain the test design and determine how the test should be performed

17
Q

Test plan

A

Defines the approach, scope, and intensity of the effort of software testing.

18
Q

Types of functional testing

A

Unit, component, integration, system,end-to-end, regression, sanity, smoke

19
Q

Types of non-functional tests

A

Performance, load, stress, volume, security, upgrade & installation, recovery, compliance

20
Q

Severity

A

Is a parameter to denote the impact of a particular defect on the software

21
Q

Priority

A

Is a parameter to decide the order in which defects should be fixed

22
Q

When to automate

A
  • the feature/product is fully ready
  • it’s repetitive
  • doesn’t change
  • high priority
23
Q

Agile ceremonies

A
  1. Sprint planning
  2. Backlog grooming - go over other stories
  3. Daily stand ups
  4. Sprint retroes
24
Q

What is epic in agile

A

A big feature that has stories

25
Q

What is spike in agile

A

Areas that doesn’t have information

26
Q

Challenges in agile

A
  1. Keep up with sprint based env
  2. Figure out how to strategize testing in 2 weeks process
27
Q

Agile software development life cycle

A

Is the structured series of stages that a product goes through as it moves from beginning to end. It has six phases:
1. concept
2. inception
3. integration
4. release
5. maintenance
6. retirement.

28
Q

About me

A
  • I have more than 5 years experience and posses a comprehensive in embedded software testing, seeking a software automation centric role.
  • Started as a support technician at Meta and worked myself up as a SQAE
  • a long the way I build a set of skills including leading a team and ability to find the bottlenecks and common pinpoints within a qa process
  • As a support technician at Meta I improved the efficiency of the overall checkout process by reducing troubleshooting time by 20% by suggesting automation
  • Within a 3 moths period I was promoted to quality analyst at Meta
  • as a quality analyst I created over 2000 and executed over 20000 test cases
  • filed over 1000 defects with 50% of high priority
  • I supported websites and mobiles apps for oculus products
  • I wanted to learn more about the processes and completed the full stack coding boot camp at UC Berkeley extension
  • after that I joined Enel X as a QAE
  • here my daily activities mostly consist of 70% manual testing and 30% automation
  • for automation I use Python with Selenium Web driver for front end, Portman with API for and learning about Appium for mobile applications.
  • About me: Personally I love dancing, hanging out with friends, reading non-fictional books and I am fascinated about human phycology and use all possible tools to learn more about it.
29
Q

Stress testing

A

Is done under abnormal conditions, makes sure that the system responds correctly to it and recovers after failure

30
Q

Agile methodology

A

Involves breaking the project into phases and emphasizes on continuous collaboration and improvement

31
Q

The difference between test plan and test strategy

A

Test plan documents scope, objective and key elements of software testing, whereas test strategy defines the techniques and approaches to testing.

32
Q

Examples of severity and priority

A

High priority high severity:
- Wrong data is displayed
High priority low severity:
- wrong logo of the company displayed(reputation)
Low priority high severity:
- app crashes when user is opening rarely used functionality on a legacy software that most users can’t access

33
Q

OOP

A

Object-oriented programming (OOP) is a programming paradigm based on the concept of objects, which can contain data and code: data in the form of fields (often known as attributes or properties), and code in the form of procedures (often known as methods)

34
Q

STLC software testing life cycle

A
  1. Requirement analysis
  2. Test planning
  3. Test case development
  4. Test environment setup
  5. Test execution
  6. Test closure
35
Q

CI/CD basics

A

Continuous integration - commit daily, it triggers automated test and notify developers of any issues
Continuous deliver - every code change that passes automation is automatically deployed to production.

Test Engineering (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions