What is Software Testing ?|Manual Testing ?|Software Testing Fundamentals|

Getting Started With Selenium Web-driver

2020-07-17T20:07:00.000+05:30

1.Browsers

The Selenium framework officially supports the following browsers:

2. Third party drivers and plug-ins

Selenium can be extended through the use of plugins. Here are a number of plugins created and maintained by third parties.

3. Locating Elements

There are eight different built-in element location strategies in WebDriver:

Locating an element

One of the most fundamental techniques to learn when using WebDriver is how to find elements on the page. WebDriver offers a number of built-in selector types, amongst them finding an element by its ID attribute:

For Example:

WebElement cheese = driver.findElement(By.id("cheese"));
driver.findElement(By.cssSelector("#cheese #cheddar"));

4. Performing actions on the AUT

Some basic actions that can be performed by Selenium Web-driver:

1) You can set an element’s text using the sendKeys method as follows:

     String name = "Charles";
     driver.findElement(By.name("name")).sendKeys(name);

2) Some web applications use JavaScript libraries to add drag-and-drop functionality.

     WebElement source = driver.findElement(By.id("source"));
     WebElement target = driver.findElement(By.id("target"));
     new Actions(driver).dragAndDrop(source, target).build().perform();

3) You can click on an element using the click method:

     driver.findElement(By.cssSelector("input[type='submit']")).click();

References

Official website of Selenium https://www.selenium.dev/
https://learnbasicsofsoftwaretesting.blogspot.com/
https://en.wikipedia.org/wiki/Selenium_(software)

Selenium Web-driver Installation

2020-07-16T22:15:00.000+05:30

Let’s get started.

Selenium supports various programming languages like Java, Python, C#, Perl, Ruby etc. Java is one of the most widely used languages for Selenium.
Selenium supports various programming languages like Java, Python, C#, Perl, Ruby etc.
Let’s begin and understand the process of Java Installation. The very first step, needed for Java installation is to configure Java environment so that later on Java codes can be used to drive the selenium.

Follow the below mentioned steps to install Selenium Webdriver

1)Open the browser and navigate to https://www.selenium.dev/

2) Click ‘Download’ menu and choose ‘Download stable version’. For Java.

3) Extract the zip file and save it in your selenium folder.

4) Add the extracted jar files into your selenium.

Reference:https://www.selenium.dev/documentation/en/

Eclipse IDE Installation

2020-07-16T11:19:00.000+05:30

Follow the below mentioned steps in order to install Eclipse IDE

Navigate to the following URL – https://www.eclipse.org/downloads/ and select the download link depending on your system architecture – (32 Bit or 64 Bit) and download it.
Once the download is over, extract the zipped file and save it to any directory. The root folder is the eclipse.
Open the folder and launch eclipse.exe.

Java Installation

2020-07-13T20:57:00.000+05:30

Follow below steps to complete your Java installation.

1) Go to the Java Downloads Page and click on the option for Java Platform (JDK). (https://www.oracle.com/java/technologies/javase-downloads.html)

2 ) In the next page, select the Accept License Agreement check box, accept it and click the download link against your matching system configuration.

3) You can run the installer once the download is over and follow onscreen instructions.

Environment Variable Set-up

1) You need to search the “Advanced system settings”
Click on ‘Environment Variables’ under ‘Advanced’ tab.

2) In the section System Variables, find the PATH environment variable and select it.

3) Click Edit. If the PATH environment variable does not exist, click New.

4) In the Edit System Variable (or New System Variable) window, specify the value of the PATH environment variable. Click OK. Close all remaining windows by clicking OK.

5) Once installation is complete, open command prompt and type “java -version”.

6) If you see the following screen you are good to move to the next step.

Reference: https://www.selenium.dev/documentation/en/

The Selenium Browser Automation

2020-07-12T11:40:00.000+05:30

Selenium

Selenium is an umbrella project for a range of tools and libraries that enable and support the automation of web browsers. At the core of Selenium is WebDriver, an interface to write instruction sets that can be run interchangeably in many browsers.

Selenium is not just one tool or API but it composes many tools.

WebDriver

If you are beginning with desktop website or mobile website test automation, then you are going to be using WebDriver APIs. WebDriver uses browser automation APIs provided by browser vendors to control browser and run tests. This is as if a real user is operating the browser. Since WebDriver does not require its API to be compiled with application code, it is not intrusive. Hence, you are testing the same application which you push live.

IDE

IDE (Integrated Development Environment) is the tool you use to develop your Selenium test cases. It’s an easy-to-use Chrome and Firefox extension and is generally the most efficient way to develop test cases. It records the users’ actions in the browser for you, using existing Selenium commands, with parameters defined by the context of that element. This is not only a time-saver but also an excellent way of learning Selenium script syntax.

Grid

Soon after the development of WebDriver tests, you may face a need of running your tests on multiple browser and operating system combinations. This is where Grid comes to the rescue.

Reference: https://www.selenium.dev/documentation/en/

Factors In Selecting Automation Testing Tool

2020-07-11T14:58:00.004+05:30

Following factors should be considered before selecting an Automation Testing tool

Identify the requirement for tools- You need to precisely identify the test tool requirements. All the requirements must be documented and reviewed by project teams and the management board.
Evaluate the tools and vendors- Analyse the commercial and open source tools that are available in the market, based on the project requirement.
Estimate cost and benefit- A cost-benefit analysis should be performed before acquiring or building a tool
Identifying and planning internal implementation (including coaching and mentoring for those new to the use of the tool).

Need for Automation Testing

2020-07-10T22:09:00.006+05:30

Need for Automation Testing

Testing manually for all the possible scenarios again and again for regression is time taking and also it won't give you result with the same efficiency as automated script will do as humans tend to commit mistake when executing the same tests again and again or efficiency won't be same each time.
Manual Testing is a monotonous job so it is very exhaustive and tiring process compared to automation.
Fewer Human Resources or does not require Human intervention .
Automation expands the speed of test execution.
Re-usability- Automation test scripts can be re-used with some modifications.
Reliability-Testing with Automation tool Improves Accuracy.
Accelerates cross-browser and cross-device testing.
Running Tests 24/7- No matter where you are in the world. You can start the tests when you leave the office and when you get back in the morning you can see the results and keep on working.

What Is a Bug?

2020-05-12T20:00:00.005+05:30

A Bug is an error,fault or mistake that doesn't allow the program to behave in predefined and desired manner and it starts behaving in unintended manner.
There are different kinds of bugs, small bugs may cause of non performance of a small part of a program, for example: while pressing menu button one can not see the menus. There could be huge bugs that can even crash the the whole program & system.

Before releasing any software to the end user, it has to go through any levels of testing.
So,the process of finding and fixing such bugs is known as "Debugging".

After rigorous testing , Testers give a detailed report about such bugs to the developers to fix it.

Causes of Bugs:

Miscommunication & Misconception: In the very first stage of requirement gathering, at times there are miscommunications between the stakeholders & Developers & testers. If this went well, at times the visualization and conceptualization goes wrong that creates bug in the software.

Erroneous Program Designs :

Erroneous Source Codes: If developers starts coding in haste without having a clear understanding of the requirements. Or the developer does not have the expertise in that particular domain.

Changing Requirements: Clients keep on changing their requirements, developers change their codes but that can have buggy effect at some other places in software.

Third Party Tools: Many tools are used to develop a software like compilers, Visual tools,Scripting Tools may have their own bugs that gets added to the given software.

Accessibility Testing

2020-03-01T16:47:00.000+05:30

Accessibility Testing can be defined as a type of Software Testing performed to ensure that the application or websites being tested is usable by people with disabilities like hearing, color blindness, old age and other specially-abled people. It is a subset of Usability Testing.

What Are Accessibility Features?

Before evaluating any Accessibility Testing tool we should be aware of what are the features needed to be incorporate in a website in order to make it accessible to everyone.
Accessibility features are designed to help people with disabilities so that they can use technology more easily.
For example, a text-to-speech feature may read text out loud for people with limited vision, while a speech-recognition feature allows users with limited mobility to control the computer with their voice.

Common Accessibility Features

1. Features for blind or low-vision computer users: Features such as text-to-speech allow users to hear what's on the screen instead of reading it. Other features, like high-contrast themes and enlarged cursors, make it easier for users with limited vision to see the screen.

2. Features for deaf or low-hearing computer users: Closed-captioning helps to convey audio information to deaf users in visual form. Mono audio systems transmit right and left audio signals through both earbuds and headphones so users with limited hearing in one ear will not miss part of what they are listening to.

3. Features for limited-mobility computer users: Keyboard shortcuts are convenient for many people, but they are especially helpful to those with difficulty physically manipulating a mouse. For users who have difficulty pressing several keys at once, sticky keys allow them to press keys one at a time to activate a shortcut.

Accessibility Features in Windows

In order to understand the accessibility more, Let’s take an example of windows Operating system which provides the wide verity of options to make it accessible to every user across the globe.
To view the accessibility features of windows user needs to go to =>Settings=> Ease of Access

1. Display

To adjust the size of text, apps, & other items, select the Start button, then select Settings=>Ease of Access=>Display.
Use the slider under Make text bigger to make just the text on your screen larger. Or, select an option from the drop-down menu under Make everything bigger to change the size of everything on your screen.

2.Cursor & Pointer Size

Make your mouse more visible by changing the colour and size of the mouse pointer. Select the Start button, then select Settings=> Ease of Access => Cursor & pointer, and choose the options that work best for you.

3. Magnify your screen

Magnifier enlarges part or all of your screen so you can see words and images better. To open Magnifier quickly, press the Windows logo key + Plus sign (+). When Magnifier is open, use Windows logo key + Plus sign (+) or Windows logo key + Minus sign (-) to zoom in or out. To close Magnifier, press Windows logo key + Esc.

4. Colour Filters

Make photos, text, and colours easier to see by applying a colour filter to your screen. Colour filters change the colour palette on the screen and can help you distinguish between things that differ only by colour.

To apply colour filters, select the Start button, then select Settings > Ease of Access > Colour filters , and choose the options that work best for you.

5.Narrator

Narrator is the built-in screen reader in Windows that reads aloud what's on your screen so you can use that information to navigate your PC. To start or stop Narrator, press the Windows logo key + Ctrl + Enter.

6. Audio

Features for deaf or low-hearing computer users: Closed-captioning helps to convey audio information to deaf users in visual form. Mono audio sy stems transmit right and left audio signals through both earbuds and headphones so users with limited hearing in one ear will not miss part of what they are listening to.

7. Speech

This app is useful for navigating menus, dictating documents, and surfing the web. It listens to your spoken words and translates them into on-screen actions. You can enable it by opening Settings > Speech and scroll down to Dictate text and control your device using only your voice.

Levels of Software Testing

2019-09-15T20:52:00.000+05:30

There are 4 levels of testing :

1. Unit Testing or Component Testing

2. Integration Testing ( Small & Large )

3. System Testing

4. Acceptance Testing (UAT – Alpha Testing, Beta Testing )

1. Unit / Component/Module Testing

1.Testing of individual software components(BS 7925 –1)
2.Also known as Unit testing, Module testing, Program testing
3.Searches for defects in, and verifies the functioning of software components(Programs, Objects, Classes, etc.)
4.Stubs ,drivers and simulators may be used
5.May include testing of functionality and specific non-functional characteristics such as memory leaks etc.
6.Also includes structural testing(e.g: branch coverage) with access to the code
7.Usually done by the programmer who wrote the code
8.Defects are typically fixed as soon as they are found, without formally recording incidents
9.Prepare and automate test cases (e.g.: J Unit)
10.BS 7925 –2 defines techniques for the design and measurement of component testing.

2. Integration Testing

“Testing performed to expose faults in the interfaces and in the interaction
between integrated components”.

Two Types:
A) Integration in the Small
B) Integration in the Large

Guidelines on selection of integration method

A) Integration Testing in the Small

Four approaches are there:-

- Top-down

- Bottom-up

- Big-bang

- Functional Incrementation Testing

Integration testing in the small

more than one (tested) component
communication between components
what the set can perform that is not possible individually
non-functional aspects if possible
integration strategy: big-bang vs incremental (top-down, bottomup,
functional)
done by designers, analysts, or independent tester.

Big-Bang Integration

In theory:

1. If we have already tested components why not just combine them all

at once? Wouldn’t this save time? (based on false assumption of no faults)

In practice:

1. Takes longer to locate and fix faults

2. Re-testing after fixes more extensive

3. End result? takes more time

Top-down Testing

Main Program is tested first
Modules are integrated one at a time
Major emphasis is on testing interfaces
Interface errors are discovered early
Test Stub’s are needed
Errors in critical modules at low levels are found late
Uses Depth-First approach
Design errors detected early

“Stubs are used as passive subprograms to allow high level control routines to be

tested when low level component is unavailable”

Stubs

Stub (Baan: dummy sessions) replaces a called component for integration testing.

Keep it Simple

1. Print/display name (I have been called)

2. Reply to calling module (single value)

3. Computed reply (variety of values)

4. Prompt for reply from tester

5. Search list of replies

6. Provide timing delay

Pros & cons of top-down approach

Advantages:

1. Critical control structure tested first and most often

2. Can demonstrate system early (show working menus)

Disadvantages:

1. Needs stubs

2. Detail left until last

3. May be difficult to "see" detailed output (but should have been tested

in component test)

4. May look more finished than it is

Bottom-up Testing:

1. Tests low-level units first

2. Modules are integrated one at a time

3. Test Driver’s s are needed

4. Errors in critical modules at low levels are found early

5. Uses Breadth-First approach

6. Design errors discovered late

“Drivers are used to run low-level modules and to test the interfaces or links

between them”

Bottom-Up Integration

Drivers

1. Driver (Baan: dummy sessions): test harness: scaffolding

2. Specially written or general purpose (commercial tools)

3. Invoke baseline

4. Send any data baseline expects

5. Receive any data baseline produces (print)

6. Each baseline has different requirements from the test driving software

Pros & cons of bottom-up approach

Advantages:

1. Lowest levels tested first and most thoroughly (but

should have been tested in unit testing)

2. Good for testing interfaces to external environment

(hardware, network)

3. Visibility of detail

Disadvantages

4. No working system until last baseline

5. Needs both drivers and stubs

6. Major control problems found last

B) Integration testing in the large

1.Tests the completed system working in conjunction with other systems.

2. LAN / WAN, communications middleware

3. Other internal systems (billing, stock, personnel, overnight batch,

branch offices, other countries)

4. External systems (stock exchange, news, suppliers)

5. Intranet, internet / www

6. 3rd party packages

7. Electronic data interchange (EDI)

Approach

Identify risks

1. Which areas missing or malfunctioning would be most critical - test them first

“Divide and conquer”

2. Test the outside first (at the interface to your system, e.g. test a package on its own)

3. Test the connections one at a time first (your system and one other)

4. Combine incrementally - safer than “big bang”

(non-incremental)

3.System Testing (ST)

Last integration step , Testing the System based on what it is supposed to do
(Functional) and how well it is doing(Non-Functional)

Test - Two Types : Functional & Non-functional

A. Functional
1. Functional requirements and requirements-based testing
2. Business process-based testing
3. Functional testing considers the external behaviour of the software (BBT)
B. Non-functional (product characteristics / requirements include):
Security, Reliability, Usability, Installability, Recovery, Interoperability etc…
1. As important as functional requirements
2. Often poorly specified

3. Must be tested , often done by independent test group.

4. Acceptance Testing: (UAT)

1. “Formal testing conducted to enable a user, customer or other authorized entity to determine whether to accept a system or

component “

2. Acceptance testing is high on the V model , a counter part to the Requirement specification process

3. Final user sign-off.

4. User Acceptance Testing:

5. Testing conducted by and visible to customer

6. It is conducted at the final stage of Validation

7. Contract Acceptance Testing:

8. A demonstration of the acceptance criteria which would have beendefined in the contract being met.

First Java Program

2019-08-29T22:29:00.000+05:30

First Java Program

Steps to be follow:

1.Open Eclipse
2.Create new java project- File-->New-->Java Project.
3. Enter the name of the project-->MyfirstJavaCode.
4.Click on Finish Button.
5.Right click on the project name and create new class. New-->Class-->Enter class name as MyfirstJavaCode.
6.Select the check box against "public static void main(String[] args)".
7.Click on Finish button.
8.Now Type " System.out.println("This is my first java program"); ". in java editor.
9.Save the program by pressing ctrl+s.
10. Right click on the program and click on "Run As" further click on " Java Application".

Actual Code:

public class MyfirstJavaCode {

public static void main(String[] args) {
// To print the message we use below mentioned code
System.out.println("This is my first java program");
}

}

Roles and Responsibilities of a Software Tester

2019-08-24T16:25:00.002+05:30

Software Tester's Roles and Responsibilities:

1. Analyzing requirement documents (SRS, FRS, BRS etc.), user stories, use cases for Project feasibility, Project scoping, and static testing.

2. Collaborating closely with the development team and other departments.

3. Execution of all levels of testing that is System testing, Integration testing, and Regression testing.

4. Designing and developing manual test cases, automation test scripts and their execution.

5. Reviewing Test Cases/scripts.

6. Finding, writing/locking and tracking software defects and inconsistencies in bug tracking system.

7. Preparing test plan document, bug reports, requirement traceability matrix and test summery reports

8. Providing timely solutions.

9. Applying quality engineering principals throughout the software product life cycle.

Automation Testing

2019-08-04T17:37:00.000+05:30

Automation Testing means utilizing a Automation software tool to execute test case scripts / test suite.

Automation testing tools can likewise enter test data into the System Under Test, think about expected and real outcomes and create itemized test reports.

Progressive development cycles will require execution of same test suite more than once. Utilizing a test automation apparatus, it's conceivable to record the test suite and re-play it as required. When the test suite is mechanized, no human intercession is required. This improved ROI of Test Automation. The objective of Automation is to decrease the quantity of experiments to be run physically and not to take out Manual Testing through and through.

Computerized programming testing is significant because of the accompanying reasons:

Manual Testing all things considered, all fields, every negative situation is time and cash consuming
It is hard to test for multilingual destinations physically
Automation does not require Human intercession. You can run computerized test unattended
Automation expands the speed of test execution
Automation enables increment To test Coverage
Manual Testing can end up exhausting and subsequently mistake inclined.

Manual Testing

2019-08-04T16:20:00.000+05:30

Manual Testing is a sort of Software Testing where Testers physically/manually execute test cases without using any automation tool for executing test cases/scripts. Manual Testing is the most crude of all testing forms and helps discover bugs in the software product .

Any new application must be manually tested before its testing is being automated. Manual Testing requires more exertion yet is important to check automation possibility.

One of the Software Testing Fundamental is "100% Automation is beyond the realm of imagination".

Types of Manual Testing

Black Box Testing
White Box Testing
Unit Testing
System Testing
Integration Testing
Acceptance Testing

Step by step instructions to perform Manual Testing

Analyse, Study and comprehend the software product documentation/guidelines. Likewise, study the Application Under Test (AUT) if accessible.
Write Test cases that describes all the requirements referenced in the documentation.
Review the test cases with Team Lead, Client (as appropriate)
Execute the test cases on the AUT
Report bugs.
When bugs are fixed, again execute the test cases to confirm they pass.

Difference between alpha and beta testing

2019-08-02T17:26:00.000+05:30

Alpha and Beta Testing has different meanings to different professionals. Alpha testing is the acceptance testing done at the development site. Some organizations have a different meaning of alpha testing. They consider alpha testing as

testing which is conducted on early, unstable versions of software. On the contrary beta testing is acceptance testing conducted at the clients end.In short, the only difference between beta testing and alpha testing is the location

where the testing process is being done.

Alpha and Beta Testing

What Is Static Testing & Dynamic Testing?

2019-06-24T23:13:00.000+05:30

Static Testing

It does not require any execution of the application under test in order to validate the functionality against the requirement. Its done by the testers and developers during the documentation (Requirement gathering and analysis,Making BRD,SRS,FRD) phase. It is more cost effective as compared to dynamic testing. It covers large area as compare to dynamic testing.

Dynamic Testing

It requires an execution of the application under test in order to validate the functionality against the requirement by entering the input and validating the output with the expected result.

Types of Software Testing

2019-06-16T20:25:00.000+05:30

As, we know the software testing is the process of finding bugs in the software and it is not a single activity. It is a collection of various activities. So therefore there is a need to identify the different types of testing. Software testing types is the categorization of software testing activities and each activity has its own strategy, objectives and deliverables.

Below is the list of common types testings :
Functional Testing :

Unit testing

Integration testing

System testing

Acceptance testing

Sanity testing

Smoke testing

Interface testing

Regression testing

Beta/Alpha testing

Non Functional Testing:

Performance Testing
Load testing
Stress testing
Volume testing
Security testing
Compatibility testing
Recovery testing
Usability testing
Compliance testing

Detailed descriptions of each testing type mentioned above

1) Unit Testing: It comes under whites box testing technique and usually performed by the developer. In this testing type individual units/components of the software are tested. The objective of the unit testing is to check the section of a code to verify its correctness. It is the very first level o software of testing.

2) Integration Testing: It is the second level of software testing. Under this testing individual units/components are combined to form a system or subsystem and then tested . The objective of this testing is to find the bugs in the interaction between the integrated units.

3) System Testing: System testing is done on fully integrated system in order to validate if the system is meeting the specified system requirement or not. It is done by the testing team under the required testing environment.

4) Acceptance Testing: Acceptance Testing is the last level of software testing under this the complete system is tested for acceptability by the client or end user. The objective of this testing is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery or not.

5) Sanity Testing: Sanity testing is deep and narrow in its approach. It is done in order to test if the build is stable and testable or not. The aim is to check that the proposed functionality works roughly as expected. If sanity testing fails then the build gets rejected to save the time and costs involved in a more rigorous testing.

6) Smoke Testing: Smoke testing is wide and shallow in its approach. It is also done to check the stability and testability of the software. It is performed "before" any functional or regression tests are executed on the software. The aim is to reject a badly broken software so that the testing team does not waste time installing and testing the software.

7) Interface Testing: Every software has various components that is server, database etc. The connection which integrates and facilitates the link between these components is termed as an Interface. the objective of this testing is to verifies that the communication between the systems are done correctly or not.

8) Regression Testing: Regression testing is done to find unexpected side effect on the existing functionality of the changes in the code. New changes can be an addition of new functionality or changes due to the fixing of the previously reported bug.

9) Alpha Testing: It is a user acceptance testing that is it is done to evaluate the system’s compliance with the business requirements at the developers side.

10) Beta Testing:It is a user acceptance testing that is it is done to evaluate the system’s compliance with the business requirements at the clients site or at end users site.

11) Performance Testing: It is done to test the performance of the software under its operational workload.

a) Speed:It is performed to test the request to response time.

b) Scalability : to know the maximum load a software can handle.

c)Stability: to know how software behaves under varying load.

12)Load Testing: It is a kind of performance testing under this software is tested to check the speed of the request to response time to know how the software will respond when multiple users uses the software simultaneously.

13) Stress Testing: Testing technique which evaluates a system or component at or beyond the limits of its specified requirements.

14) Volume Testing: This testing is done to know the behavior of the software under varied volume of the data handled by the software.

15) Security Testing: The objective of security testing is to identify the threats,security risk and loopholes in the software and to measure its potential vulnerabilities, so the software does not stop functioning or is exploited by the hackers. It also helps in detecting the security risks in the software so that the developers can fix the security issues.

16)Compatibility Testing: It is performed to check if the software is compatible with the hardware,operating system, and with different browsers or not.

17) Recovery Testing: Recovery Testing is performed to check how well a software product can recover from crash, hardware failures.

18)Usability Testing: It is performed to test "How user friendly" a software product is. It mainly focuses on end users if the software is easy to use and can operate the software easily.

19)Compliance Testing: Compliance testing checks if the software has developed in accordance with standards, procedures and guidelines.

Advantages and Disadvantages of V-model

2019-06-08T09:57:00.001+05:30

Advantages of V-model:

• Simple and easy to use. Testing activities like planning, test designing happens well before coding. This saves a lot of time. Hence higher chance of success over the waterfall model.
• Proactive defect tracking – that is defects are found at early stage.
• Avoids the downward flow of the defects.
• Works well for small projects where requirements are easily understood.

Disadvantages of V-model:

• Very rigid and least flexible.
• Software is developed during the implementation phase, so no early prototypes of the software are produced.

When to use the V-model:

• The V-shaped model should be used for small to medium sized projects where requirements are clearly defined and fixed.
• The V-Shaped model should be chosen when ample technical resources are available with needed technical expertise.

Types of Verification

2019-06-02T15:24:00.000+05:30

As we know that Verification is basically reviewing any application without running it.
So we can do verification in two ways. Namely, Walkthroughs & Inspection.

Broadly speaking Walkthroughs are informal way of verification wherein we ask our colleague or we can our self verify the documentation & coding.

On the other hand, Inspection is a Formal & Official way of Verifying. For Example, an organisation may have a separate team for carrying out inspection by verifying design documents for every project.Every project needs to go through this process and if there is any mistake in design document then the project will get non conformance list and for proceeding further every project needs to go through this.

Introduction to White Box Testing, Black Box Testing.

2019-06-02T13:51:00.001+05:30

Black Box Testing is based on requirements and specifications. Black box testing requires no knowledge of internal code, structures, or implementation of the software product being tested.

White Box Testing is based on internal code, internal structures, and implementation of the software product being tested. White box testing generally requires detailed programming skills.

The below mentioned figure shows how both types of testers view an accounting application. How black box testers view the application. While during white box testing the tester knows the internal structure of the application. In most scenarios white box testing is done by developers as they know the internals code, structures of the application. In black box testing we check the overall functionality of the application while in white box testing we do code reviews, view the architecture, remove bad code, and
do unit level testing.

White Box Testing, Black Box Testing and Gray Box Testing

What are the different software development models?Software Development Life Cycle Models Methodologies|SDLC Models: Agile,Waterfall, V-Model,Spiral

2019-05-29T17:31:00.001+05:30

Software Development Models

There are mainly 5 models :

1. Waterfall Model

2. Spiral Model / Iterative Model

3. V-model

4. RAD

5. Agile Model & Scrum basics

1. Waterfall Model

A Waterfall model is characterised by three attributes.

1. The project is divided into separate, distinct phases.

2. Each phase communicates to the next through pre-specified outputs.

3. When an error is detected, it is traced back to one previous phase at a time, until

it gets resolved ay some earlier phase.

Advantages :

1. The main strength of Waterfall model is its simplicity

2. Focus on one stage a time

Disadvantages :

1. Late attention to the testing activity

2. Errors are more costly to correct

3. Testing is seen as a test execution phase

4. Difficult to deal with the changes

Waterfall Model

2. Spiral / Iterative Model

The Spiral Life Cycle Model is a type of iterative software development model which is generally implemented in high risk projects. It was first proposed by Boehm. In this system development method, we combine the features of both waterfall model and prototype model. In Spiral model we can arrange all the activities in the form of a spiral.
Each loop in a spiral represents a development phase (and we can have any number of loops according to the project). Each loop has four sections or quadrants

To determine the objectives, alternatives and constraints
Risk analysis and evaluation of alternatives
Execution of that phase of development
Planning the next phase

Spiral / Iterative Model

Spiral model is also called as meta-model because in a way it comprises of other models of SDLC. Both waterfall and prototype models are used in it.

Advantages :

1) Spiral Life Cycle Model is one of the most flexible SDLC models in place. Development phases can be determined by the project manager, according to the complexity of the project.

2) Project monitoring is very easy and effective. Each phase, as well as each loop, requires a review from concerned people. This makes the model more transparent.

3) Risk management is one of the in-built features of the model, which makes it extra attractive compared to other models.

4) Changes can be introduced later in the life cycle as well. And coping with

these changes isn’t a very big headache for the project manager.

Disadvantages:

1) Cost involved in this model is usually high.

2) It is a complicated approach especially for projects with a clear SRS.

3) Skills required, to evaluate and review project from time to time, need expertise.

3. V- Model : Verification & Validation:

Development tasks and testing tasks are corresponding activities of equal importance.

V-Model distinguishes between different test levels where each test level is a testing against its corresponding development level.

Testing is not seen as phase which happens at end of development.

V-model is derived from waterfall model

Within each test level, it must be checked whether the outcomes of

development meet the specified requirements of those requirements that are relevant on this specific level of abstraction.

V- model means Verification and Validation mode .

Each phase must be completed before the next phase begins.

Testing of the product is planned in parallel with a corresponding phase of development.

V-model

V-model phases ( Left branch – Verification/ Static )

•Requirements like BRS and SRS begin the life cycle model just like the waterfall model. But, in this model before development is started, a system test plan is created. The test plan focuses on meeting the functionality specified in the requirements gathering.
• The high-level design (HLD) phase focuses on system architecture and design. It provide overview of solution, platform, system, product and service/process. An integration test plan is created in this phase as well in order to test the pieces of the software systems ability to work together.
• The low-level design (LLD) phase is where the actual software components are designed. It defines the actual logic for each and every component of the system. Class diagram with all the methods and relation between classes comes under LLD. Component tests are created in this phase as well.
• Coding: This is at the bottom of the V-Shape model. Module design is converted into code by developers. The implementation phase is, again, where all coding takes place. Once coding is complete, the path of execution continues up the right side of the V where the test plans developed earlier are now put to use.

The V-model – Right branch (Verification/Dynamic)

• Unit testing : Verifies whether each unit performs correctly according to its specification
• Integration testing: Checks if groups of units collaborate in the way that is specified by the high level design.
• System testing: Verifies whether the system as a whole meets the specified requirements
• Acceptance testing: (UAT – α & β ) Checks if the system meets the
requirements, as specified in the contract , from the customers point of view.

Verification Vs. Validation
Verification

1. Verification is also known as

Static testing.

2. Disciplined approach to

evaluate whether a software

product fulfils the requirement

or conditions imposed on them

(Are we doing the job right ) ?

3. Done by systematically reading

the contents of software product

with intention of defecting

defects.

4. Helps in identifying not only

the presence of defects but also

their location.

5. It is the process of confirming

that s/w “meets its

specifications”.

6. Method : Walkthrough,

Inspection, Review of each

software product

Validation

1. Validation is also known as

Dynamic testing.

2. Disciplined approach to

evaluate whether the final ,

as-built software product

fulfils its specific intended use

(Are we doing the right Job?)

3. Done by systematically testing

a software product with the

intention of finding defects.

4. Helps in identifying the

presence of defects , not their

location

5. It is the process of confirming

that s/w “meet the user

requirements”.

6. Method : Unit testing ,

Integration testing , System

testing , Acceptance testing ,

Functional

Adv. & Dis-adv. of V-model Advantages of V-model:

Advantages of V-model:

• Simple and easy to use. Testing activities like planning, test

designing happens well before coding. This saves a lot of time. Hence higher chance of success over the waterfall model.

• Proactive defect tracking – that is defects are found at early stage.

• Avoids the downward flow of the defects.

• Works well for small projects where requirements are easily understood.

Disadvantages of V-model:

• Very rigid and least flexible.

• Software is developed during the implementation phase, so no early prototypes of the software are produced. When to use the V-model:

• The V-shaped model should be used for small to medium sized projects where requirements are clearly defined and fixed.

• The V-Shaped model should be chosen when ample technical resources are available with needed technical expertise.

Water Fall Vs. V-Model

Waterfall Model: It includes all phases of SDLC but the drawback is once requirement made freezed it cannot be changed.
Waterfall Model the tester role will take place only in the test phase
Waterfall model is a fixed process u can't make any changes in the
requirement or in any phase
waterfall model used only the requirements are fixed.
V-Model: In this model all phases will be done correspondently development and testing.
V-Model role will take place in the requirement phase itself
V-Model u can make any changes in the requirements
V-model is the simultaneous process but it is not in case of water fall model
V-model can be used for the any type of requirement(Uncertain requirement)

4. RAD

•In general, RAD approaches to software development put less emphasis on planning tasks and more emphasis on development.

• In contrast to the waterfall model, which emphasizes rigorous specification and planning, RAD approaches emphasize the necessity of adjusting requirements in reaction to knowledge gained as the project progresses.

• This causes RAD to use prototypes in addition to or even sometimes in place of design specifications.

• RAD approaches also emphasize a flexible process that can adapt as the project evolves rather than rigorously defining specifications and plans correctly from the start

RAD

5.Agile Software Development

Agile software development primarily focuses on an iterative method of development and delivery.

A software testing practice that follows the principles of agile software development is called Agile Testing. Agile is an iterative development methodology, where requirements evolve through collaboration between the customer and self-organizing teams and agile aligns development with customer needs.

Developers and end users communicate closely and the software is built.

Customer is thus closely involved in the software design and development process.

Delivery timelines are short and new code is built on the previous one.

Agile Development models : Extreme Programming (XP) , SCRUM

Advantages of Agile Testing:

• Agile Testing Saves Time and Money

• Less Documentation

• Regular feedback from the end user

• Daily meetings can help to determine the issues well in advance.

Best Practices in Agile Testing

1. Automated Unit Tests

2. Test Driven Development

3. Automated Regression Tests

4. Exploratory Testing

Principles of Agile Testing

• Testing is NOT a Phase: Agile team tests continuously and continuous testing is the only way to ensure continuous progress.

• Testing Moves the project Forward:When following conventional

methods, testing is considered as quality gate but agile testing provide feedback on an on going basis and the product meets the business demands.

• Everyone Tests: In conventional SDLC, only test team tests while in agile including developers and BA's test the application.

• Shortening Feedback Response Time: In conventional SDLC, only during the acceptance testing, the Business team will get to know the product development, while in agile for each and every iteration, they are involved and continuous feedback shortens the feedback response time and cost involved in fixing is also less.

• Clean Code: Raised defects are fixed within the same iteration and thereby keeping the code clean.

• Reduce Test Documentation: Instead of very lengthy documentation, agile testers use reusable checklist, focus on the essence of the test rather than the incidental details.

•Test Driven: In conventional methods, testing is performed after

implementation while in agile testing, testing is done while

implementation.

Agile Software Development

Prioritization of Tests

2019-05-29T11:42:00.000+05:30

Prioritization of Tests :

Why do we need to Prioritize ?

Time constraints
Resource Constraints
We need to get the best done in the time available
How do we Prioritize?
Identification of the Most Important Tests first(MITs)

Basis of Prioritization of Tests:

Business complexity.
Severity of potential failure
Visibility of failure
Likelihood of error
User requirements and priorities
Technical complexity and complexity
Contractual requirements / Compliance requirement

The Psychology of Software Testing

2019-05-29T11:37:00.002+05:30

The Psychology of Testing

Building the software requires a different mindset from testing the software.
Building is aimed to solve problems with testing is to look for defects (find problems) in software.
Programmers and Testers are two separate roles, although programmers do test code.
Test independence avoids author bias and is often more effective at finding defects and failures.
Developers view : Testing is the process to prove that software works correctly.
QA view : Testing is the process to prove that software does not work.
Manager’s View : Testing is the process to detect the defects and minimize the risk associated with the residual defects.

Why do we test?

Primarily to find faults in the software
This can be perceived as being a destructive process, not constructive
How does this fit with the mind set of the developer and tester ?

Tester-Developer relationships:

Communication is the Key !!

Must be constructive not destructive
Developers must inform testers of any changes made to the system
Testers must report problems to developers clearly and concisely.

It is a two-way process !!

Test Independence:

Independent testing is more effective.

Author should not test their own work.
The author should not test their own work

-Assumptions made are carried into testing

-People see what they want to see

-There can be emotional attachment with the product

-We’re human

Levels of Independence

Where test cases are
designed by the person who writes the software under test (v.v.low)
designed by another person(low)
designed by people from another department (medium)
designed by people from another organisation (very medium)
not chosen by a person (v.v.high)

Testers characteristics:

Methodical
Happy when they are finding faults
Under-valued by the organisation
Not always intended to be a tester
Good communicators
Need to be multi-talented
Tact & diplomacy are essential

Developer characteristics :

Specialized
Creative
Valued by the organisation
Trained
Sensitive to criticism

Software Testing Life Cycle / Fundamentals Test Process

2019-05-29T11:23:00.003+05:30

Fundamentals of Software Testing Process/ STLC

1.Test Planning:

1.Determine the scope and risks and identify the objectives of testing.

2. Determine the test approach

3. Implement the test policy and/or the test strategy.

4. Determine the required test resources.

5. Schedule test analysis and design task, test implementation, execution

and evaluation.

6. Determine the exit criteria

2. Test Control:

1. Measure and analyse the results of reviews and testing.

2. Monitor and document progress, test coverage and exit criteria.

3. Provide information on testing.

4. Initiate corrective actions.

3. Test Analysis & Design:

1.Review test basis (such as product risk analysis, requirements, architecture, design specs) that help us build our tests.

2. Identify gaps and ambiguities in the specifications.

3. Identify test conditions – high level list of what are we interested in testing.

4. Evaluate test-ability of the requirement and system – ex: if performance of the software is important , that should be specified in a testable way.

5. Design the test environment set-up and identify and required infrastructure and tools.

4. Test Implantation:

1. Develop and prioritize our test cases, using the techniques and create test data.

2. Priority of test cases, decided during test planning should be taken in account.

3. Create test suites from test cases for efficient test execution.

4. Test suite is a logical collection of test cases which naturally work together.

5. Implement and verify the environment – make sure appropriate hardware and

software has been set up.

5. Test Execution:

1. Execute the test suites and individual test cases, this can be done manually or using automated tools.

2. Log the outcome of the test execution and record identities.

3. Logging should be done for each and every test case run for success or failure. This can be use for test analysis.

4. Re-execute tests to confirm fix, also called as re-testing.

6. Evaluating exit criteria and reporting:

1. Evaluating exit criteria is the activity where test execution is assessed against the objectives.

2. This should be done fir each test level

Ex : Exit criteria for unit testing:

a) all unit test cases are executed.

b) No open defects exists in the unit.

3. It’s very important to collect metrics in order to decide the end of the test

4. May require change in test plan ex: addition of resources, addition/deletion of tests.

7. Test Closure:

1. Major activity is to collect data from completed test activities. ( Test results/notes of unexpected events ).

2. Finalize and archive test ware, such as scripts, test environments, and any test infrastructure.

3. Hand over test-ware to the maintenance organisation.

4. Analyse lessons learned for future releases and projects.

General Software Testing Principles

2019-05-29T11:05:00.001+05:30

There are 7 Principles related to software testing:

Principle 1- Testing shows presence of defects
Principle 2- Exhaustive testing is impossible
Principle 3- Early testing
Principle 4- Defect clustering
Principle 5- Pesticide Paradox
Principle 6- Testing is context dependent
Principle 7- Absence-of-errors fallacy

Detailed explanation

Principle 1- Testing shows presence of defects : The principle arises from the theory of the process of scientific experimentation has been adopted by testers;

Testing can only prove the presence of defects, never their absence.

The aim of testing is to make the software fail by finding bugs.In case testers are unable to find defects after repeatedly doing regression testing doesn’t mean that the software is bug-free.

Principle 2- Exhaustive testing is impossible :Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risks and priorities to focus testing efforts.

For example, nuclear power installations, air traffic control systems and fly-by-wire systems. Indeed, it is important that these systems are tested more thoroughly than most; but exhaustive testing is not possible.

Example : A simple function adds two 32 bit numbers and returns a result Assumption:1000 test cases can be executed per second.

Principle 3- Early testing:Testing activities should start as early as possible in the software development. Early testing such as early test design and review activities finds defects early on when are cheap to find and fix.

Early testing has following advantages:

a. Early preparation of test environment, thereby preventing any delays and

unknown risks will have enough time to deal with.

b. If you complete test cases early you will have a baseline. If there are changes

later , problem will be easy to detect by comparing it with baseline.

c. You will have time to Quantify the problem's scope.

d. You may find that few items may not be tested , since they may not be

impacted. This input can cut down on your Testing phase.

e. There is usually tendency to squeeze the testing time. This may impact

Quality. But if you start testing early , you may not need to squeeze your time.

Principle 4 - Defect clustering :A small number of modules contains most of the defects discovered during pre-release testing or show the most operational failures.

In most cases, it can be seen that the majority of the detected defects are caused by a small number if modules.

All of us experience traffic congestion's. Typically, during these congestion's, we will see a convoy effect. There will be stretches of roads with very heavy congestion's, with vehicles looking like

they are going in a convoy. This will be followed by a stretch of smooth sailing (rather , driving) until we encounter the next convoy.

Principle 5 - Pesticide Paradox: If the same tests are repeated over and over again , eventually the same set of test cases will no longer find any new bugs.

To overcome this ‘pesticide paradox’, the test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software.

Example : If you keep applying the same pesticide , the insects eventually build up resistance and the pesticide no longer works.

Principle 6 - Testing is context dependent: Not all software systems carry same level of risk and not all problems have the same Impact when they occur.

Example : Safety –critical software is tested differently from an e-commerce site.

Principle 7- Absence-of-errors fallacy: Finding and fixing defects does not help if the system built is unusable and does not fulfill the users needs and expectations.

What is Software Testing ?|Manual Testing ?|Software Testing Fundamentals|

Getting Started With Selenium Web-driver

1.Browsers

2. Third party drivers and plug-ins

3. Locating Elements

Locating an element

4. Performing actions on the AUT

References

Selenium Web-driver Installation

Let’s get started.

Follow the below mentioned steps to install Selenium Webdriver

Eclipse IDE Installation

Follow the below mentioned steps in order to install Eclipse IDE

Java Installation

Follow below steps to complete your Java installation.

Environment Variable Set-up

The Selenium Browser Automation

Selenium

WebDriver

IDE

Grid

Factors In Selecting Automation Testing Tool

Following factors should be considered before selecting an Automation Testing tool

Need for Automation Testing

Need for Automation Testing

What Is a Bug?

Causes of Bugs:

Accessibility Testing

Levels of Software Testing

A) Integration Testing in the Small

Big-Bang Integration

Top-down Testing

Stubs

Pros & cons of top-down approach

Bottom-up Testing:

Bottom-Up Integration

Drivers

Pros & cons of bottom-up approach

B) Integration testing in the large

Approach

4. Acceptance Testing: (UAT)

First Java Program

Roles and Responsibilities of a Software Tester

Software Tester's Roles and Responsibilities:

Automation Testing

Computerized programming testing is significant because of the accompanying reasons:

Manual Testing

Types of Manual Testing

Step by step instructions to perform Manual Testing

Difference between alpha and beta testing

What Is Static Testing & Dynamic Testing?

Static Testing

Dynamic Testing

Types of Software Testing

Advantages and Disadvantages of V-model

Advantages of V-model:

Disadvantages of V-model:

When to use the V-model:

Types of Verification

Introduction to White Box Testing, Black Box Testing.

What are the different software development models?Software Development Life Cycle Models Methodologies|SDLC Models: Agile,Waterfall, V-Model,Spiral

Software Development Models

1. Waterfall Model

Waterfall Model

2. Spiral / Iterative Model

Spiral / Iterative Model

3. V- Model : Verification & Validation:

V-model

V-model phases ( Left branch – Verification/ Static )

The V-model – Right branch (Verification/Dynamic)

Verification Vs. ValidationVerification

Validation

Adv. & Dis-adv. of V-model Advantages of V-model:

Water Fall Vs. V-Model

4. RAD

RAD

5.Agile Software Development

Advantages of Agile Testing:

Principles of Agile Testing

Agile Software Development

Verification Vs. Validation
Verification