Tag: Quality Assurance

Reliable Sources To Learn About Website Testing And Be Successful

About Website Testing

Software testing is the process of reviewing a system or its component(s) to find if it completes the specified requirements or not. Testing is the process of executing a system in order to find any gaps, errors, or missing requirements in terms of the actual requirements.

In testing, a Test Scenario is what to be tested and a Test Case is how to be tested. In other words, a test scenario is a group of test cases.

Test Scenario

This is used to test  the end-to-end functionality of a software application and ensure the business processes and flows are functioning as per requirements. The tester thinks themselves as if end users and find real world scenarios (use-cases) that can be performed in testing. Once these test scenarios are completed, test cases can be written for every scenario. As Test scenarios are the concept of what to test.

Test Case

A test case is a collection of steps to be executed by the  tester team in order to validate every scenario’s. A test scenario usually has multiple test cases related with it, as test cases layout the low-level details on how to test the scenario.

Types of testing

There are different types of methods that can be used for software testing as following:

Functional testing:

  • Black box testing: In this method, it is used without having any knowledge of the internal process of the application is called black-box testing.
  • Unit testing: This kind of testing is firstly performed by developers before the actual testing given  to the testing team to formally execute the test cases for checking the functionality as per client’s requirements.
  • Integration testing: Integration testing is defined as the combination of the tested part of application to check if they function correctly or not as before.
  • Equivalence partitioning testing: In this method, set of test condition are divided into a equal partition that can be considered for example there is a range in input field like age limit, value, etc.
  • Boundary value testing: This method is used between extreme ends or boundaries between partitions of the input values for example greater than or less than some value.
  • Exploratory testing: As its name implies, it is about exploring, finding out about the software that what it does, what it doesn’t do, what works and what doesn’t work and decide with time.
  • Usability testing: Usability testing basically the testers tests the ease with which the user interfaces can be used which is user-friendly or not.
  • Design Testing: Designing testing is eye attracting & simple -through all browser & operating system(MAC,Windows & Ubuntu), with responsiveness of every page in different orientation, (add on like whatfont, page rular).
  • Functionality Testing: Functionality testing is user friendly, working as per client’s requirements- for all browser, OS & orientation & responsiveness- should work same as per requirements or functions defined as before.
  • Compatibility Testing: Compatibility testing is a type of software testing which is used to check the compatibility of the system/application/website built with various other objects such as other web browsers(IE, Firefox, Chrome, Safari), hardware platforms, users (in case if it’s very specific type of requirement, such as a user who speaks and can read only a particular language), operating systems( Mac, Windows, Ubuntu)  etc.
  • Regression Testing: Regression testing is performed to verify that a fixed bug/error hasn’t affected in another functionality/application or business rule violation of the system.

Non-functional testing:

Performance Testing: Performance testing is a non-functional testing method which is performed to determine the system parameters/requirements in terms of responsiveness and stability under various workload according to internet speed, loading time.

How does testing help businesses?
Our company’s testimonial for testing: Time to make efforts to break what we built. We QA to ensure proper standards being followed for a Quality Outcome and latest devices compatibility.

Hope this blog helps you to get the strategic idea for your testing journey. You can also refer our informative testing steps and Share your views and feedback.


How to Start Testing Journey

“QA is not only about finding mistakes, it’s about Quality”.

As it proved your first impression is your last impression & as specially for tester’s there are so many stones as bugs in your testing ways. To help you to start your testing journey with some quick & interesting points review the below mentioned basic points to startup.

  • First Check Cases for blank fields or use the alternate blank fields.
  • Check the Whole site for spelling mistakes.
  • Tool tips text should be meaningful
  • Default page sorting should be provided.
  • In any form, one radio button must be marked by default.
  • All numeric values should be formatted properly.
  • For all fields, there should be a placeholder text or example value.
  • The validation message should not contain any data like no/ not. It should be in a positive way.
  • The data or field can’t be overlapped in any resolution.
  • Check  time & proper validation i.e image size 8 MB, supporting document i.e .pdf .zip, .csv, display properly while uploading time. An image should not be blur & if an image is not loaded or displayed then, it should show the alt text.
  • All error messages should be displayed in same CSS style (e.g. using red color) and General confirmation messages should be displayed using CSS style other than error messages style (e.g. using green color).
  • Dropdown fields should have first entry as text like ‘Please Select’.
  • Delete/update functionality for any record on the page should ask for confirmation.
  • Check all input fields for special characters.
  • Check broken links throughout the application/software.
  • Check broken Images throughout the application/software.
  • Check Date & font- family consistency throughout the site.
  • Check All button & links with having functionality & same consistency for CSS throughout the site.
  • Amount values should be displayed with correct currency symbols.
  • Reset button functionality should set default values for all fields.
  • Check Add & edit contents with added details, it should be the same.
  • Application crash or unavailable pages should be redirected to a custom error page.
  • The links which are provided in email for verification must be linked(proper URL) & clickable on every provider and have an expiry time.
  • Perform browser compatibility test site in the different browser (i.e google chrome, Mozilla, Safari, i.e.) Perform OS compatibility Test application with different

    OS like mac and windows.

  • Dummy/test content must be removed from the site after testing.

Hope this blog helps you to get the basic way to start up your testing journey. You can also refer our types of testing blog and Share your views and feedback.