Testing by Stages of the Project

Planning Phase

At this stage, the product is defined by the team of Engineers, Marketers and Sales Staff. Hence, testing approach at this phase is majorly focused on scrutinizing the idea rather than source codes.
Reviewers or Testers gather data with the help of following planning and design tools:

• Comparative Product Evaluations: this approach aims to answer three questions:
  • What is the competitive advance of this product in the market?
  • How is the competitor doing better?
  • Which of their features can be included in this product?

Reviewers accumulate data from all the available sources like competitor’s product description, available demos, etc., and write their own product description with features, SWOT analysis and any other important information.

• Focus Groups: in this approach, a Tester decides a topic, focus and scope of a discussion around the product. Then a group of participants representing a particular market segment are asked to give their unbiased opinions and views on that topic. The objective of such Focus Group Testing is to measure the current market demand and trend of the product.
• Task Analysis: a test crucial for designing the user interface, task analysis is used by Reviewers to observe how the potential users can employ it to complete their tasks and meet their goals.

Design Stage

During this phase of Software Development, Designers work to figure out how to provide planned competencies of the product. Divided in two forms, Internal Design explains the internal working of the product, while the External Design describes the product from user’s perspective.

When it comes to software testing at the Design stage, a Tester needs to review how the system, built according to the design, will work. This can be done with the help of Review Meetings, that are used to identify problems with the design. It can be performed in three ways:

• Walkthrough: the program is simulated to show how it will work, how different pieces of system will work, etc. to highlight the redundancies and missed details.
• Inspection: this technique focuses on handling errors, conforming with the standards and other defined areas, etc.
• Technical Review: in this review meeting, Testers discuss the issues related to the program and list down the problems that needs to be changed and redesigned.

Development Stage

During this stage software construction, defect diagnosis and prevention strategies are synchronized to reduce development risk, time and cost. The main objective of testing at this phase is to eliminate errors, increase quality as well as efficiency of the software, before it proceeds to the Quality Assurance phase.

Development Testing can be classified into different types, depending on the Company’s expectations:- data flow analysis metrics analysis, code coverage analysis, Static Code Analysis, Traceability, Peer Code Review, etc.

After Development but before Testing, developers use exhaustive Code Review Checklist. This checklist is used to check the Functionality of the codes along with exception handling and correct propagation of errors; their Readability and Maintainability including naming conventions, standard formatting, intuitive naming of variables, flexibility of the code and verifications of whether the code is configurable or not; and Performance or Efficiency that will address all language specific pitfalls, and will include areas like  Concurrency management, Memory leaks, Buffer overflows, Array indexing, pointer arithmetic, proper termination of threads, etc.

Click Labs is giving away a comprehensive Code Review Checklist, with separate sections on Functionality, Readability and Maintainability, and Performance or Efficiency. Register your Name and Email Now, and be the first one to receive this well detailed checklist for your smooth Code Reviewing.

Testing Stage

Last but not the least, Testing Phase includes the following tests listed below, that have been explained above:

• Acceptance Test
• Control Flow
• Data Flow and Integrity Test
• Stress Test
• User Interface
• Regression Test
• Performance Test
• Beta Test
• Release Test

Read More

Black-Box Testing or Behavioural Testing

Contrary to the White-Box Testing, Black-Box Testing examines the functionality of a software program, rather than its internal structure. Another point of differentiation is that, unlike in Glass-Box Testing, the tester only requires knowledge on what the software does.

This type of testing includes-

• Equivalence Partitioning technique: test design technique in which  input data units are divided into into partitions of similar data, from which representative values from partitions are tested.
• Boundary Value Analysis: it involves specifying the boundaries for input values, and testing the selected values that are at and inside/outside the boundaries
• All-Pairs Testing: in this testing method of combinations, all discrete combinations of input parameters are tested.
• Decision Table Testing: In this approach, Decision Tables like flow-charts and switch-case statements are used to associate conditions with actions.
• Cause-Effect Graph: this testing includes identifying input (cases) and output (effects) conditions, producing graph and test cases accordingly.
• Error Guessing: it is a type of software testing in which conditions or variables, that are used to find bugs in software system, are determined based on tester’s intuition and experience in previous testing.

Since Black-box testing deals with the application from the end user perspective, a tester does not examine source codes. As a result, he/she is likely to leave some or most parts of software program unexamined.

Read More

Glass Box Testing or White Box Testing

This type of software testing involves examining the internal structure, design, implementation and working of the software program. During this test, a Tester use design test cases are with the help of programming skills and internal perspective of the system. He/ She then selects inputs to exercise paths through the code and determine the result.

White-Box Testing is applicable at the levels, be it Unit Testing level for testing paths within units, Integration Testing level for for testing paths between units, or System Level for testing paths between sub-systems.

Various techniques that are used in Glass box Testing are

• API Testing for applications using private and public APIs;
• Code Coverage for satisfying criteria of code coverage;
• Fault Injection for measuring the efficiency of testing strategies by creating faults;
• Mutation Testing for evaluating quality of existing test and designing new ones
• Static Testing for testing the sanity of software code, algorithm or document.

Even though White-Box Testing is a thorough process and can be initiated at the early stages, it is a highly complex testing approach and misses out the evaluation of functionality part of the software.

Read More

Testing By Objectives

Acceptance Testing

This test is conducted to determine that the software system complies with the customer’s requirements and is ready to be delivered to them. Every feature is checked from the user’s perspective by the testing team and the feature is marked accepted or rejected. The results of these tests are very subjective in nature and it takes a while to figure out the exact issue in the code.

Installation Testing

This type of Quality Assurance testing ensures that the installed system on the target environment i.e. customer’s hardware is working properly. Along with the verification of installation procedure, it is used for system testing in accordance with the hardware configuration requirements.

Alpha-Beta Testing

Alpha Testing is a form of internal acceptance test, in which simulated or actual  operational testing is done at the developer’s site. The tested software is then released to a limited number of audience who are not in the developing team, to ensure that the software has zero number of bugs. This type of external acceptance test is called Beta Testing

Functional Testing

Also known as Conformance Testing or Correctness Testing, this test is used to validate whether a particular function is as per the specifications or not. The recorded results answer “can the user do this” or “does this particular feature work.”

Regression Testing

Generally, regression in a software occurs as a result of program changes, when an existing code collides with the new one. In this scenario, Regression Testing is done by retesting of selective units or system, to check whether the previously tested software is still functioning properly or not.

Performance Testing

This type of testing is used to substantiate that the software system or sub-system meets the stated performance requirements like response time and capacity. It also investigates and measures other attributes like reliability, scalability and resource usage.

Stress Testing

Also known as Torture Testing, it exercises intense examination of the software which are beyond normal operational capacity and design load. This testing is used to determine breaking points and modes of failure, and to test the stability of the software outside its comfort zone.

Usability Testing

This technique is used to assess if the user interface is easy to learn and use by the customer. It is concerned with the use of software, user documentation, how it functions and recovers from the user errors.

Security Testing

This test is required to look for any loopholes in the security mechanism of the software system for complete protection and functionality of data. It includes elements of integrity, confidentiality, availability,  non-repudiation, authorization and authentication.

Read More

Levels of Software Testing

Unit Testing or Component Testing

It is the first and the most basic level of Software Testing, in which a single unit (i.e. a smallest testable part of a software) is examined in isolation from the remaining source code. Unit Testing is done to verify whether a unit is functioning properly. In other words, it checks the smallest units of code and proves that the particular unit can work perfectly in isolation. However, one needs to make sure that when these units are combined, they work in a cohesive manner. This directs us to other levels of software testing.

Integration Testing

After Unit Testing, software components are clubbed together in large aggregates and tested, to verify the proper functioning, performance and reliability between units, and expose any defect in the interface. This process is known as Integration Testing. It can be performed in two ways-
• Incremental Testing: testing in the traditional and structured way, this classic approach follows a hierarchical path. It can further be divided into two days:
  • Top-Down Testing: in this approach, top level integrated units are tested first, followed by step by step examination of lower level modules.
  • Bottom-Up Testing: contrary to the top-down approach, this method facilitates testing at the lower level first, and then taking it up the hierarchy. It is generally practiced where bottom-up development process is followed.
  • Sandwich Testing: this approach is the hybrid of Top-Down Testing and Bottom-Up Testing
• Big Bang Testing: in this approach, most or all of the software modules are put together at once, and then tested. Even though Big Bang testing saves a lot of time, the results recorded are not always accurate. This might result in complications and prevent the developing team to achieve their testing goals.

System Testing or End-to-End Testing

After identifying functional bugs at the Unit and Integration testing level, System Testing is done to scrutinize the entire software system. The objective of this test is to verify the non-functional part of the software like speed, security, reliability and accuracy. Evaluation of external interfaces like applications, hardware devices, etc. is also done at this time. System Testing is also done to ensure that the software meets the customer’s functional and business requirements.

Read More

Test Cases for Reset Password

1.Check the forget password link is there in the reset pwd screen.

2.After clicked link page should navigate to forgot password page.

3. Enter the Invalid answer for the wrong Secret Question in the drop down list (should display alert message, force the user to fill correct answer)

4. Enter the Valid answer for the wrong Secret Question in the drop down list(should display alert message, force the user to fill the correct question & Answer)

5. Enter the invalid answer for the correct secret question in the drop down list(should display alert message, force the user to fill the correct answer)

6. Enter the valid answer and valid secret Question in drop down list (should generate temperory password and send to user, via mail or displayed according to requirement)

7. User entered the username and temperary password in the login page.( Page navigates to the Change password page, force the user to change the temp password)

Read More

Test Cases for forget password

1.To check whether when we select the forgot password link it is directing to forgot password link page.

2.when click sumnit button show validation msg.

3.when enter alternat email show validation msg this email is not register.

4.To check whether in that page it must ask for alternative email id to send the link

5.To check whether the link has sent to the mail to which the user has provided
or register.

5.To check whether the link can be used once once

6.Check whether when we click the link it must open a new link page

8.Check whether it must ask the user to enter new password

9.Check whether the entred new password and re-type password must be the same

10.Check whether when we login wiht new password it must sign in to our account

Read More

Test Case for Register page

Check the availability of the fields or objects email,full name , Pwd, cofinrm pwd

Check the spellings of all place holder or filed name

check the mandatory fields in the form

check the error messages for unfill of all mandatory fields

Check for the error message for unfill of email id

check for the error message for fill email address as “zubaer”

check for the error message for fill email address as “#@%^%#$@#$@#.com”

check for the error message for fill email address as “@gmail.com ”

check for the error message for fill email address as “zubaer < zubaer@luutaa.com>”

check for the error message for fill email address as “zubaer.luutaa.com”

check for the error message for fill email address as “zubaer@luutaa@luutaa.com”

check for the error message for fill email address as “. zubaer@luutaa.com”

check for the error message for fill email address as “zubaer.@luutaa.com”

check for the error message for fill email address as “zubaer..k@Luutaa.com”

check for the error message for fill email address as “ zubaer@gmail.com (zubaer)”

check for the error message for fill email address as “ zubaera@luutaa”

check for the error message for fill email address as “ zubaer@luutaa..com”

check for the error message for fill email address as “zubaer@-luutaa.com”

check for the error message for fill email address as “ zubaer@111.222.333.444”

check the error message for special characters for Full name

check the error message for more than 20 characters for full nmae

check for the error message for mobile no by enter more than 10 numbers

check for Password should contain combination of letter, numbers and symbols.--------

check for Password should not contain spaces.

check for Password should not be more than 40 characters.

check for confirm Password should contain combination of letter, numbers and symbols
which is same as the password.

check for confirm Password should not contain spaces.

check for confirm Password should not be more than 40 characters.

Check the successful message for entry of all mandatory fields with the proper input.

Read More

Test Case for login page

Verify the mandatory fields in Login screen.(without entering data in the text fields)

User Name and Password field are appearing in proper position In the page or not.

User name and password fields are having same font, proper look up feeling or not.

User name and password field are properly aligned.

Verify the Login Buttons in Login screen-Login

Check the spellings are proper are not.

Button fields are active and doing desired work or not.

Verify the validation message when trying to login by leaving any username and password fields.

Verify the validation message shown when trying to login by leaving username field.

Verify the validation message shown when trying to login by leaving password field.

Verify the error message after logging when wrong User name using.
(Enter valid password but invalid username.)

Verify the error message after logging when wrong Password using.
(Enter valid username and invalid password)

Verify the error message after logging when wrong User name and Password using.
(Enter invaild username, password)

Verify the error message after logging when long username , that exceeds the limit of characters(20) using.

Verify the error message after logging when long Password ,that exceeds the limit of characters using.

Try copy/paste in the password text box.

Verify if user is able to login to Application when using correct credentials.

Read More

zubaer khan on google

zubaer khan on google

Read More

zubaer khan mhow

zubaer khan mhow

Read More

zubaer khan wikipedia

zubaer khan Wikipedia   zubaer khan  Wikipedia

Read More

zubaer khan Experience

zubaer khan Experience

5 yrs Experience of Software Test engineer

Read More

THOUGHT OF THE DAY by zubaer khan

THOUGHT OF THE DAY by zubaer khan

Read More

zibraan khan s/o zubaer khan

zibraan khan s/o zubaer khan

Read More