Software Testing - Wikitechy

What is GUI Testing ?

Editor — Sun, 18 Jul 2021 19:18:52 +0000

What is GUI Testing ?

It is the process of ensure to proper functionality of the graphical user interface (GUI ).
It may also given by the application and making sure it confirms to its written specifications.
GUI testing evaluates design elements such as layout, colors, fonts, font sizes, labels, text boxes, text formatting, captions, buttons, lists, icons, links and content.
GUI testing processes can be either done by the two categories are manual or automatic, and are often performed by third -party companies, rather than developers or end users.
It can be require a lot of programming and is time consuming whether manual or automatic.
Usually the software author writes out the intended function of a menu or graphical button.
GUI testing also tends to test for certain program behaviors that users expect, like an hourglass when the program is busy.

GUI Testing Methods

Manual-based testing.
Record-reply testing.
Model-based testing.

Manual Based Testing

Manual testing is a testing process that is carried out manually in order to find defects without the usage of tools or automation scripting.
A test plan document is prepared that acts as a guide to the testing process in order to have the complete test coverage.

Manual Based Testing

Record and Replay

In this method, GUI testing can be done using automation tools.
This is also been divided by the two parts.
During Record, test steps are captured by the automation tool.
During playback, the recorded test steps are executed on the Application Under Test.
Example of tools – QTP.

Record and Replay

Model Based Testing

In this model, it is a graphical description of a system’s behavior.
It helps us to understand and predict the system behavior.
Models help in a generation of efficient test cases using the system.

Model Based scheduling

GUI Testing Tools

Ranorex.
Selenium.
QTP.
Cucumber.
Silk Test.
Test Complete.
Squish GUI Tester.

Features

Consistency.
Effectiveness.
User-Friendliness.
Functionality.
Significance

What is SDLC ?

Editor — Sun, 18 Jul 2021 19:16:03 +0000

What is SDLC ?

Software Development Life Cycle (SDLC) is a set of phases that provide a common understanding of the software building process.
How the software is realized and developed from the business understanding and requirements elicitation phase to convert these business ideas and requirements into functions and features until its usage and operation to achieve the business needs.
Generally a software engineer should have enough knowledge on how to select the SDLC model based on the project context and the business requirements.
Therefore, it may be required to choose the right SDLC model according to the specific concerns and requirements of the project to ensure its success.
You can think of SDLC models as tools that you can use to better deliver your software project. Therefore, knowing and understanding each model and when to use it, the advantages and disadvantages of each one are important to know which one is suitable for the project context.

What is SDLC

There are some various software development life cycle models defined and designed which are followed during the software development process. These models are also referred as Software Development Process Models”.
Each process model based on a Series of rules unique to its type to ensure success in the process of software development.

Following are the most important and popular SDLC models followed in the industry & miuns

- Waterfall Model
- Iterative Model
- Spiral Model
- V-Model
- Big Bang Model

Waterfall model

The waterfall is a widely accepted SDLC model. In this approach, the whole process of the software development is divided into various phases. In this SDLC model, the outcome of one phase acts as the input for the next phase.
This SDLC model is documentation-intensive, with earlier phases documenting what need be performed in the subsequent phases.

Incremental Approach

The incremental model is not a separate model. It is essentially a series of waterfall cycles.
The requirements are divided into groups at the start of the project. For each group, the SDLC model is followed to develop software.
The SDLC process is repeated, with each release adding more functionality until all requirements are met. In this method, every cycle act as the maintenance phase for the previous software release.
Modification to the incremental model allows development cycles to overlap. After that subsequent cycle may begin before the previous cycle is complete.

V-Model

In this type of SDLC model testing and the development, the phase is planned in parallel.
So, there are verification phases on the side and the validation phase on the other side. V-Model joins by Coding phase.

Agile Model

Agile methodology is a practice which promotes continue interaction of development and testing during the SDLC process of any project.
In the Agile method, the entire project is divided into small incremental builds. All of these builds are provided in iterations, and each iteration lasts from one to three weeks.

SDLC Phases

Phase 1: Requirement collection and analysis
Phase 2: Feasibility study
Phase 3: Design
Phase 4: Coding
Phase 5: Testing
Phase 6: Installation/Deployment
Phase 7: Maintenance

Phase 1: Requirement collection and analysis

The requirement is the first stage in the SDLC process. It is conducted by the senior team members with inputs from all the stakeholders and domain experts in the industry.
Planning for the quality assurance requirements and recognization of the risks involved is also done at this stage.

Phase 2: Feasibility study

Once the requirement analysis phase is completed the next step is to define and document software needs.
This process conducted with the help of ‘Software Requirement Specification’ document also known as ‘SRS’ document.

There are mainly five types of feasibilities checks:

Economic: Can we complete the project within the budget or not ?
Legal: Can we handle this project as cyber law and other regulatory framework/compliances.
Operation feasibility: Can we create operations which is expected by the client ?
Technical: Need to check whether the current computer system can support the software
Schedule: Decide that the project can be completed within the given schedule or not.

Phase 3: Design

In this third phase, the system and software design documents are prepared as per the requirement specification document. This helps define overall system architecture.
This design phase serves as input for the next phase of the model.There are two kinds of design documents developed in this phase,

High-Level Design (HLD)

Brief description and name of each module
An outline about the functionality of every module
Interface relationship and dependencies between modules
Database tables identified along with their key elements
Complete architecture diagrams along with technology details

Low-Level Design(LLD)

Functional logic of the modules
Database tables, which include type and size
Complete detail of the interface
Addresses all types of dependency issues
Listing of error messages
Complete input and outputs for every module

Phase 4: Coding

Once the system design phase is over, the next phase is coding. In this phase, developers start build the entire system by writing code using the chosen programming language.
In the coding phase, tasks are divided into units or modules and assigned to the various developers. It is the longest phase of the Software Development Life Cycle process.
In this phase, Developer needs to follow certain predefined coding guidelines. They also need to use programming tools like compiler, interpreters, debugger to generate and implement the code.

Phase 5: Testing

Once the software is complete, and it is deployed in the testing environment. The testing team starts testing the functionality of the entire system.
This is done to verify that the entire application works according to the customer requirement.

Phase 6: Installation/Deployment:

Once the software testing phase is over and no bugs or errors left in the system then the final deployment process starts.
Based on the feedback given by the project manager, the final software is released and checked for deployment issues if any.

Phase 7: Maintenance

Bug fixing – bugs are reported because of some scenarios which are not tested at all
Upgrade – Upgrading the application to the newer versions of the Software
Enhancement – Adding some new features into the existing software

What is Agile testing ?

Editor — Sun, 18 Jul 2021 19:13:35 +0000

What is Agile testing ?

Agile testing refers to a software testing practice that follows different principles of agile software development.
In other words, agile testing means testing software for defects or any other issues quickly or within the context of agile and give quick feedback for better and faster development of the project.

What is Agile Testing

Testing and development run parallel in agile testing. The tester’s role lies not in identifying defects in the application but in behaving as a developer and bringing in improvements, suggestions, and test cases to be included in the application.
In agile testing, testers follow the entire lifecycle but due to constant feedback and regular interaction between developers and customers, the application can be delivered in a short time without compromising on the quality.
The tester and developers respond to quick changes in the application rather than following a fixed plan.

The principles of agile testing are:

- Testing is NOT a phase,
- Everyone participates in the testing process,
- It shortens the response time of feedback,
- Reduces test documentation.

Agile testing requires continuous interaction between developers, customers, managers, stakeholders, and testers.
Testing is an important component of each phase of the developmental process.

Test Plan for Agile

Unlike the waterfall model, in an agile model, a test plan is written and updated for every release.
The agile test plan includes types of testing done in that iteration like test data requirements, infrastructure, test environments, and test results.
Typical test plans in agile includes

- Testing Scope,
- New functionalities which are being tested,
- Level or Types of testing based on the features complexity,
- Load and Performance Testing,
- Infrastructure Consideration,
- Mitigation or Risks Plan,
- Resourcing,
- Deliverables and Milestones.

Agile Testing Strategies

Agile testing life cycle spans through four stages.

What is Software Testing Life Cycle(STLC) ?

Editor — Sun, 18 Jul 2021 19:11:05 +0000

What is Software Testing Life Cycle(STLC) ?

Software Testing Life Cycle (STLC) is the testing process which is executed in systematic and planned manner.
In STLC process, different activities are carried out to improve the quality of the product.

Following steps are involved in Software Testing Life Cycle (STLC). Each step is have its own Entry Criteria and deliverable.

Requirement Analysis
Test Planning
Test Case Development
Environment Setup
Test Execution
Test Cycle Closure

What is Software Testing Life Cycle(STLC)

Requirement Analysis

Requirement Analysis is the very first step in Software Testing Life Cycle (STLC). In this step Quality Assurance (QA) team understands the requirement in terms of what we will testing & figure out the testable requirements.
If any conflict, missing or not understood any requirement, then QA team follow up with the various stakeholders like Business Analyst, System Architecture, Client, Technical Manager/Lead etc., to better understand the detail knowledge of requirement.

Test Planning

Test Planning is most important phase of Software testing life cycle where all testing strategy is defined.
This phase also called as Test Strategy phase. In this phase typically Test Manager (or Test Lead based on company to company) involved to determine the effort and cost estimates for entire project.

Test Case Development

The test case development activity is started once the test planning activity is finished.
This is the phase of STLC where testing team write down the detailed test cases. Along with test cases testing team also prepare the test data if any required for testing.
Once the test cases are ready then these test cases are reviewed by peer members or QA lead.

Test Environment Setup

Setting up the test environment is vital part of the STLC. Basically test environment decides on which conditions software is tested.
This is independent activity and can be started parallel with Test Case Development. In process of setting up testing environment test team is not involved in it.

Test Execution

Once the preparation of Test Case Development and Test Environment setup is completed then test execution phase can be kicked off.
In this phase testing team start executing test cases based on prepared test planning & prepared test cases in the prior step.

Test Cycle Closure

Call out the testing team member meeting & evaluate cycle completion criteria based on Test coverage, Quality, Cost, Time, Critical Business Objectives and Software.
Discuss what all went good, which area needs to be improve & taking the lessons from current STLC as input to upcoming test cycles, which will help to improve bottleneck in the STLC process.

What is the difference between System and Functionl Test Case ?

Editor — Sun, 18 Jul 2021 19:08:53 +0000

What is the difference between System Test Case and Functionality Test Case ?

What is Test case

A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly.
The process of developing test cases can also help find problems in the requirements or design of an application.

Difference between System and Functional Test Case

System Testing

System testing aims to figure out whether the whole system fulfills the requirements given to it.
System Test Case will be developed to validate the System as a whole End-to-end, while combining it with the required HW, Database, Networking and any other connections such as Printers, Fax or any other external. Supporting SW application.
Here, while an input is given to the System, the System’s behavior to handle the input data and its final expected output will be verified.
System testing take a look at the typical stop product. which includes each unmarried module, interface and every minute details along with all inner and external additives of the system.
Gadget checking out fundamental reason is to find out whether or not the complete gadget fulfills the requirements as given to it.
Using tools might be powerful for system testing.
Device trying out describes how right the product works.

System testing

Functional Testing

Functional testing aims to figure out whether given functionality works as specified.
Functional Test Cases whole be developed to validate the Application according to the functionality demanded by the client or provided in the SRS.
The input is given to the application, the application behavior to handle the input data and its final expected output will be verified.
Useful checking out take a look at the functionalities of the product. which incorporates strain, load, safety, overall performance and many others.
Manual checking out or automation gear may be used for functional checking out.
Functional checking out describes what the product does.

What is Deployment ?

Editor — Sun, 18 Jul 2021 19:06:36 +0000

What is Deployment ?

Deployment includes all the process required for preparing a software application to run and operate in a specific environment. It involves installation, configuration, testing and making changes to optimize the performance of the software. It can either be carried out manually or through automated systems.
The advantages of Deployment,
- Time saving
- Enhance security
- Monitor User Actions
- Effective software updates

I have recorded a test over web application (with IE6.0) in analog mode. But, while running it my test gets failed. Why ?

Editor — Sun, 18 Jul 2021 19:04:48 +0000

I have recorded a test over web application(with IE6.0) in analog mode. But, while running it my test gets failed. Why ?

Analog mode records depend on screen as well as followed window.
It means if you record related to screen then it basically depends on position of the window.
While recording if you place window somewhere else and while running script you might be moved the window somewhere else. That’s why script is failing.

Write test case for Banking Application ?

Editor — Sun, 18 Jul 2021 19:00:20 +0000

Write test case for Banking Application ?

Test case is the smallest unit of the testing plan, which includes a description of necessary actions and parameters to achieve and verify the expected behavior of a particular function or the part of the tested software.
If you have a task to check some functionality, you can create a test script or user story. So, you need to understand where to start testing, which general steps need to be executed and what the result should be And then this scenario is broken down into more detailed parts – test cases – to define all positive, negative, localization and other behaviors of the software.

We create a test scenario as:

The user must be logged.
Move to the “upload photos” page.
Click the “upload” button.
Select photos and Upload them.
Verify all visitor links.
Verify all Customer links.
Verify Customer login with valid data.
Verify Customer login with invalid data.
Verify Customer login without data.
Verify Banker login with valid data.
Verify Banker login with invalid data.
Verify Banker login without data.
Verify Admin login with valid data.
Verify Admin login with invalid data.
Verify Admin login without data.
Verify all Admin home links.
Verify Admin change password with valid data.
Verify Admin change password with invalid data.
Verify Admin change password without data.
Verify Admin change password with existing data.
Verify admin logout.
Create a new user with valid data.
Create a new user with invalid data.
Create a new user without data.
Create a new user with existing branch data.
Update user with valid data.
Update user with invalid data.
Update user without data.
Update user with existing data.
Verify that user is able to make financial transactions to added recipient.
Verify that user is able to add decimal number into amount ( limited by 2 numbers).
Verify that user is not able to add negative number into amount field.
Verify that user is allowed to transfer money only if there is proper account balance.
Verify that there is a confirmation check for financial transactions.
Verify that user is given an acknowledgment receipt upon successful financial transaction.
Verify that customer is able to send money to multiple people.

Write the test cases on prime number with result ?

Editor — Sun, 18 Jul 2021 18:59:01 +0000

Write the test cases on prime number with result ?

Let the prime number be n.
Divide the number n by 1 remainder=0 pass.
Divide the number n by n remainder=0 pass.
Divide the number n by 2 remainder!=0 pass.
Divide the number n by up to n-1 and if remainder not equal zero, then it is a prime number.

Prime Number Algorithm

Example

 
function primeTester (n) {
 //take out edge case 0 and 1
 if(n<=1) 
 return false;
  
 //go from 3 since 2 is a prime number
 for(var i=3; i   //check if n is divisible by i
   if(n%i ===0 ) 
   return false
 }
 
 //if passed all out test
 return true;
}

Write 3 test cases on MS-WORD ?

Editor — Sun, 18 Jul 2021 18:56:42 +0000

Write 3 test cases on MS-WORD ?

Check whether there is MS office in the system.
If we open MS word the default page should be blank.
Check for the Menu options. Whether it has basic functionalities for the file to open, save, save as, edit, copy etc

Write the test cases on ATM for security purpose ?

Editor — Sun, 18 Jul 2021 18:54:03 +0000

Write the test cases on ATM for security purpose ?

Verify the ATM card insertion.
Verify the ATM card insertion in wrong angle.
Verify invalid ATM card insertion.
Verify PIN entry.
Verify invalid PIN entry.
Verify invalid PIN entry continually 3 times.
Verify account type selection.
Verify invalid account selection.

Write 3 test cases on railway reservation system ?

Editor — Sun, 18 Jul 2021 18:52:05 +0000

Write 3 test cases on railway reservation system ?

Verify there is a train available to the destination.
Verify the seats are available on the particular date.
Verify the seats available for required coach that is A/c or Sleeper coaches.

Write 3 main test cases for excel sheet ?

Editor — Sun, 18 Jul 2021 18:25:02 +0000

Write 3 main test cases for excel sheet ?

Click on Start – Program file – MS Office
Check Ms-Excel in that MS office.
Check Whether Ms-Excel is opening or not.
Check the window blank sheet of excel sheet.
If you close the window asking “are you want save? or not
If you click ‘yes’ ask where you want save give the path otherwise cancel.

How to configure yahoo cookies in load runner ?

Editor — Sun, 18 Jul 2021 18:22:58 +0000

How to configure yahoo cookies in load runner ?

The web_add_cookie() function adds a new cookie.
If the name and path match an existing cookie, the existing cookie is overwritten with the new one.
If the “expires” date has past, the cookie is deleted.

Note

Users don’t use (access or modify) the cookies that are stored by your browser. Instead, each user uses the cookies that are sent to the Vuser by the server host at runtime.
These cookies are maintained only temporarily while the Vuser script runs. The web-cookie functions (web_add_cookie, web_remove_cookie, and web_cleanup_cookies) manipulate these temporary cookies only.

What is known Issue ?

Editor — Sun, 18 Jul 2021 18:20:48 +0000

What is known Issue ?

Issue is nothing but a defect in US terminology, they use issue instead of defect or bug.
The defect/Bug which is present in the current (release) build, When there is sufficient time to fix the bug, the development team releases the build with bugs.
These bugs will be mentioned in the release notes as Known bugs. Normally these(bug) issues will be fixed in the future builds or releases.

What is Defect Leakage and Latency bug ?

Editor — Sun, 18 Jul 2021 18:18:05 +0000

Defect Leakage:

If the client reports any bug that is called Defect Leakage.
These are the defects which are not identified during the software testing process but found by the clients and given as feed back.
It is calculated as. (Number of defects slipped)/(Number of defects received-Number of defects withdrawn)*100.

Latency bug:

An exposed or unidentified bug which exists in the system over a period of time is known as the Latent Bug. The bug may persist in the system in one or more versions of the software.
The bug which is not identified in present version and can be able to identified in Later versions.

What is the Gap Analysis ?

Editor — Sun, 18 Jul 2021 18:15:24 +0000

What is the Gap Analysis ?

Gap analysis is a business resource assessment tool enabling a company to compare its actual performance with its potential performance.
It’s a formal Study of what business is doing today and can be conducted in different Prespectives, like.
- Organization (e.g., human resources).
- Business direction.
- Business processes.
- Information technology.

Gap analysis

The three steps to follow the gap analysis,
- Analyze your current state
- Identify the ideal future state
- Bridge that gap

Analyze your current state

Start your current state analysis can include qualitative information such as team processes/methodologies, and quantitative information, such as the number of sales calls made each week.
In fact, your gap analysis process should evaluate everything you currently do so you get the “great image.”

Identify the ideal future state

The gap analysis report should also include a column labeled “Future State,” which outlines the target condition the company wants to achieve.
Like the current state, this section can be drafted in concrete, quantifiable terms, such as aiming to increase the number of fielded customer calls by a certain percentage within a specific time period; or in general terms, such as working toward a more inclusive office culture.

Bridge that gap

This gap analysis report should list all the possible solutions that can be implemented to fill the gap between the current and future states.
These objectives must be specific, directly speak to the factors listed in the gap description above, and be put in active and compelling terms.
Next steps include hiring a certain number of additional employees to field customer calls; instituting a call volume reporting system to guarantee that there are enough employees to field calls; and launching specific office diversity programs and resources.

What is the difference between “call to action” and “call an existing action” ?

Editor — Sun, 18 Jul 2021 18:11:26 +0000

Call to Action:

Any action can be called with in the text or with in the another text.The call action by default QTP creates copy of action.
The changes made in call to action, will be reflected in original action(from where the script is called). But where as in call to copy Action , the changes made in the script will not effect the original script(Action).

Call to Action

Call to Existing Action:

It is reusable action with in the text or with in the another text. QTP creates a link to called action and make to statements as read only calling actions.

What is mutation testing ?

Editor — Sun, 18 Jul 2021 18:08:15 +0000

Mutation Testing is a software testing where we mutate (change) certain statements in the source code and check if the test cases are able to find the errors.
It is a type of White Box Testing which is mainly used for Unit Testing.
The changes in mutant program are kept extremely small, so it does not affect the overall objective of the program.
The aim of Mutation Testing is to assess the quality of the test cases which should be robust enough to fail mutant code. This method is also called as Fault based testing strategy as it includes creating fault in the program.
Mutation Testing is widely used for languages such as Java and XML.

What is Mutation Testing

Benefits of Mutation Testing

Mutation Testing carries a entire new kind of errors to the developer’s attention.
Mutation Testing is the most powerful method to detect hidden defects, which might be impossible to identify using the conventional testing techniques.
Tools such as Insure++ help us to find defects in the code using the state of the art.
Increased customer fulfillment index as the product would be a smaller amount of errors.
Debugging and Maintaining the product would be more easier than ever.

What is meant by preconditions and postconditions in a Test Case ?

Editor — Sun, 18 Jul 2021 18:02:09 +0000

Preconditions:

A precondition of an operation is an assertion which must be true just before the operation is called.
Anything that the solution can assume to be true when the use case begins is known as preconditions.

Preconditions and Postconditions in Testing

Post Conditions:

A postcondition of an operation is an assertion which must be true just after the operation has been completed.
A postcondition means if the operation returns the desired result, or has the desired effect, relative to the given parameters that satisfy the precondition.