QA intro

Decimal

A fraction number. שבר עשרוני.

Test Scenario

As a tester, you may put yourself in the end user's shoes and figure out the real-world scenarios and use cases of the Application Under Test. Test Scenarios can be approved by various stakeholders like Business Analyst, Developers, Customers to ensure the Application Under Test is thoroughly tested. It ensures that the software is working for the most common use cases. For studying the end-to-end functioning of the program, Test Scenario is critical.

BRD

Business Requirement Document

Specs

Functional specifications

Automated Testing

Goal of Automation is to reduce number of test cases to be run manually and not eliminate manual testing all together. Automated testing is recommended only for stable systems and is mostly used for Regression Testing. The boring part of executing same test cases time and again, is handled by automation software in automation testing. Tools to Automate Manual Testing Selenium QTP Jmeter Loadrunner TestLink Quality Center(ALM)

Software Build

If you are developing a simple computer program which consists of only one source code file, you merely need to compile and link this one file, to produce an executable file. This process is very simple. Usually this is not the case. A typical Software Project consists of hundreds or even thousands of source code files. Creating an executable program from these source files is a complicated and time-consuming task. You need to use "build" software to create an executable program and the process is called " Software Build"

IEEE

Institute of Electrical and Electronics Engineers.

RTM

Requirements Traceability Matrix. A document that maps and traces user requirement with test cases. The main purpose of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality should miss while doing Software testing. Parameters include Requirement ID Risks Requirement Type and Description Trace to design specification Unit test cases Integration test cases System test cases User acceptance test cases Trace to test script

SDLC

SDLC is Software Development Life Cycle. It is the sequence of activities carried out by Developers to design and develop high-quality software. Though SDLC uses the term 'Development', it does not involve just coding tasks done by developers but also incorporates the tasks contributed by testers and stakeholders. In SDLC, test cases are created.

STLC

STLC is Software Testing Life Cycle. It consists of series of activities carried out by Testers methodologically to test your software product. Though STLC uses the term "testing" it does not involve just testers, at some instances, they have to involve developers as well.

Smoke Testing

Software Testing performed after software build to ascertain that the critical functionalities of the program is working fine. It is executed "before" any detailed functional or regression tests are executed on the software build. The purpose is to reject a badly broken application, so that the QA team does not waste time installing and testing the software application. cover the most important functionality or component of the system. Smoke testing exercises the entire system from end to end. Smoke testing is like General Health Check Up.

SRS

System requirement specifications

System Testing

System testing is the testing of a complete and fully integrated software product. Usually software is only one element of a larger computer based system. Ultimately, software is interfaced with other software/hardware systems. System testing is actually a series of different tests whose sole purpose is to exercise the full computer based system. Two Category of Software Testing Black Box Testing White Box Testing

TRD

Technical Requirement Document

Test Formality

Testing is a very formal activity, and is documented in detail. The degree of formality depends on the type of application under test , standards followed by your organization ,& maturity of development process.

Extreme Programming

Tests are written before the code Rely heavily on testing frameworks All classes in the applications are tested Quick and easy integration is made possible

Test case

The description of what requirement is being tested The explanation of how the system will be tested The test setup like: version of application under test, software, data files, operating system, hardware, security access, physical or logical date, time of day, prerequisites such as other tests and any other setup information pertinent to the requirements being tested Inputs and outputs or actions and expected results Any proofs or attachments Use active case language Test Case should not be more than 15 steps Automated test script is commented with inputs, purpose and expected results Setup offers alternative to pre-requisite tests With other tests, it should be incorrect business scenario order

Hardware/Software Testing

This is when the tester focuses his/her attention on the interactions between the hardware and software during system testing.

V- Model

V- model is an extension of the waterfall model. Unlike waterfall model, In V-model, there is a corresponding testing phase for each software development phase. Testing in V-model is done in parallel to SDLC stage. Testing is done as a sub project of SDLC.

Waterfall Model

Waterfall model is a sequential model divided into different phases of software development activity. Each stage is designed for performing specific activity during SDLC phase. Testing phase in waterfall model starts only after implementation of the system is done. Testing is done within the SDLC.

Manual testing

a type of Software Testing where Testers manually execute test cases without using any automation tools. Manual testing is the most primitive of all testing types and helps find bugs in the software system. #In fact any type of software testing type can be executed both manually as well using an automation tool.

Integer

any of the natural numbers, the negatives of these numbers, or zero. Opposite- decimal.

Acceptance testing

beta testing of the product done by the actual end users.

Test Basis

defined as the source for creation of test Cases.

Unit Test

done during the development (coding) of an application. commonly automated, but may still be performed manually. Unit testing relies on mock objects being created to test sections of code that are not yet part of a complete application. Mock objects fill in for the missing parts of the program. Tools: jsAsserUnit Rational Software- IBM Dotunit CUT

Recovery Testing

done to demonstrate a software solution is reliable, trustworthy and can successfully recoup from possible crashes.

Migration Testing

done to ensure that the software can be moved from older system infrastructures to current system infrastructures without any issues.

Integration Testing

individual software modules are integrated logically and tested as a group. A typical software project consists of multiple software modules, coded by different programmers. Integration testing focuses on checking data communication amongst these modules. Hence it is also termed as 'I & T' (Integration and Testing), 'String Testing' and sometimes 'Thread Testing'. The Software Industry uses variety of strategies to execute Integration testing , viz. Big Bang Approach- small systems Incremental Approach: which is further divided into following Top Down Approach Bottom Up Approach Sandwich Approach - Combination of Top Down and Bottom Up

Regression Testing

involves testing done to make sure none of the changes made over the course of the development process have caused new bugs. It also makes sure no old bugs appear from the addition of new software modules over time. Tools- Selenium, QTP, RTF

Functional Testing

involves trying to think of any possible missing functions. Testers might make a list of additional functionalities that a product could have to improve it during functional testing.

Sanity Testing

kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing. Sanity testing is usually not documented and is unscripted. Sanity testing exercises only the particular component of the entire system. Sanity Testing is like specialized health check up.

Usability Testing

mainly focuses on the user's ease to use the application, flexibility in handling controls and ability of the system to meet its objectives

Load Testing

necessary to know that a software solution will perform under real-life loads.

Non-functional Testing

requirements like performance, usability, load factor that are also important.

Framework

set of automation guidelines which help in Maintaining consistency of Testing Improves test structuring Minimum usage of code Less Maintenance of code Improve re-usability Non Technical testers can be involved in code Training period of using the tool can be reduced Involves Data wherever appropriate four types: Data Driven Automation Framework Keyword Driven Automation Framework Modular Automation Framework Hybrid Automation Framework

String

מחרוזת. sequence of characters (i.e., letters, numerals, symbols and punctuation marks). An important characteristic of each string is its length, which is the number of characters in it. The length can be any natural number(i.e., zero or any positive integer). A particularly useful string for some programming applications is the empty string, which is a string containing no characters and thus having a length of zero. A substring is any contiguous (רצף) sequence of characters in a string.