Posts

Security Testing

Security testing is a process that is performed with the intention of revealing flaws in security mechanisms and finding the vulnerabilities or weaknesses of software applications. The prime objective of security testing is to find out how vulnerable a system may be and to determine whether its data and resources are protected from potential intruders. Online transactions have increased rapidly of late making security testing as one of the most critical areas of testing for such web applications. Security testing is more effective in identifying potential vulnerabilities when performed regularly.   Normally, security testing has the following attributes:    ● Authentication  ● Authorization  ● Confidentiality  ● Availability  ● Integrity  ● Non-repudiation  ● Resilience   Why is Security Testing Important?    A comprehensive security testing framework deals with validation across all layers of an applica...

URL and COOKIES

Uniform Resource Locator (URL):    URL is an acronym for Uniform Resource Locator and is a reference (an address) to a resource on the Internet. URLs occur most commonly to reference web pages (Http) but are also used for file transfer (FTP), email (mailto), database access (JDBC), and many other applications.    A URL has two main components:    Protocol identifier: ​ For the URL http://example.com, the protocol identifier is Http.   Resource name:​ For the URL http://example.com, the resource name is example.com.    The resource name is the complete address to the resource. The format of the resource name depends entirely on the protocol used, but for many protocols, including HTTP, the resource name contains one or more of the following Components:   Host Name:​ The name of the machine on which the resource lives.  Filename: ​The pathname to the file on the machine.  Port Number: ​ The port number to ...

Web Applications testing

Web application testing, a software testing technique exclusively adopted to test the applications that are hosted on the web in which the application interfaces and other functionalities are tested.  Web Application Testing - Techniques:   1. ​Functionality Testing ​:​   Below are some of the checks that are performed but not limited to the below list:  ● Verify there is no dead page or invalid redirects.  ● First, check all the validations on each field.  ● Wrong inputs to perform negative testing.  ● Verify the workflow of the system.  ● Verify data integrity.   2. ​Usability testing​ :​ To verify how the application is easy to use with.  ● Test the navigation and controls.  ● Content checking.  ● Check for user intuition.  3.​ Interface testing ​: ​ Performed to verify the interface and the dataflow from one system to another.   4.​ Compatibility testing ​: ​  Compatibility te...

Configuration Control Board (CCB)

CCB Team Member ​:    ● Project Manager ​: ​ The Role of the project manager. A project manager is a person who has the overall responsibility for the successful initiation planning design execution monitoring controlling and closure of a project.   ● Client representative ​:  ​ This is the person responsible for managing the project on behalf of the client. This may be an individual from within the client's organization or maybe a consultant.   ● Quality Manager​ :  ​ Quality assurance managers provide training in best practices. They aim to make production employees responsible for managing their own quality standards.   ● Contract Manager ​: ​ The contract manager is the management of contracts made with customers' vendors partners or employees. The personnel involved in contract administration required to negotiate support and manage effective contracts are often expensive to train and retain.   ● Funding Ma...

Identified for Configuration Management

The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...

Software Configuration Management (SCM)

Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...

Attributes of a Defect Report

A defect report is a document that identifies and describes a defect detected by a tester. The purpose of a defect report is to state the problem as clearly as possible so that developers can replicate the defect easily and fix it.  Defect Report Template:    ID​ :  ​A unique identifier is given to the defect. (Usually, automated)   Project ​:  ​Project name.   Product: ​Product name.   Release Version: ​ Release version of the product. (e.g. 1.1.3)   Module ​: ​Specific module of the product where the defect was detected.   Defect Priority​ ​: ​Priority of the Defect.   Defect Severity ​: ​Severity of the Defect.   Summary ​: ​Summary of the defect. Keep this clear and concise. Description Detailed description of the defect. Describe as much as possible but without repeating anything or using complex words. Keep it simple but comprehensive.    Expected Results ​: ...