Need to do software testing

-

Need To Do Software Testing

 Software testing is very important ​because​ of the following reasons:  


  1. Software testing is necessary because we all make mistakes and we need a process to identify those mistakes.   
  2. Software testing is important to find ​defect​ and errors in new and prevalent applications and websites.  
  3. Testing of any product (website/application) is necessary to validate whether the product works as per the expectation.  
  4. It is important to ensure the application should not show any failures because it can be more expensive and dangerous in the future.  
  5. Testing helps the client to gain confidence.  
  6. The cost of errors in software can vary from nothing at all to large amounts of money and even the loss of life.   

   

 ​Examples: 

A social application is delivered to the customer with few bugs in its source user and destination user will suffer some problem due to bugs in the application.
So he may quit using this social application. 

So here:   

An application does not satisfied customers needs or expectations.
Application is not fit for purpose.   
Software testing is really required to point out the defects and errors that were made during the development phases. 

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

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...
Read more

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...
Read more