SUBSCRIBE HERE TO GET POST UPDATES VIA EMAIL :

Delivered by FeedBurner

GUI testing, full form of GUI testing Graphical User Interface. Main focus of GUI testing to test the appearance of the software instead of functional requirements.UI of application a comes first when someone browse to our application the first impression will be based on UI. If it is attractive interactive and easy to use then the visitor stay in our site for longer period. But if our applications UI is poor, miss-aligned, images are broken, buttons links are grayed out, application not conveying anything then visitors feel uncomfortable as soon as possible. UI help a lot to attract the visitors and keep visitor on site for longer period.

The Question is how to perform GUI testing and what do we need to test while performing GUI testing.the following things need to be tested while performing GUI testing.

  • Page content
  • Buttons
  • Menus
  • Icons present on page
  • Pop ups
  • Color
  • Images   

Lets discuss each points.

Earlier we have already learnt about some basic things about synchronizing timer and how to use it on controller level on software load test plan in my previous post. Now here we will discuss and learn how to use synchronizing timer on request level in software load test plan and how it will works. Let's understand with example.

Let first understand the meaning of RISK, risk means a problem or issue or bug which can occur in future.so risk may related to software or it may also related to QA or development team. Means guessing the possible which can come in near future and finding the solution for that in advance or change the situation so that it will never happen.

Risk analysis is also an important part to perform Risk Based Testing. There are many situation where risk analysis help. Many of you might have come across such a situation when there is a project but the requirements are poorly written, incomplete requirement, unclear requirement, or not testable requirements. some in such a situation if development team start developing with unclear , incomplete requirements then definitely at a point they will face a major issue which will either unsolvable or it will takes lots of time which effect on software delivering dead line. If we performed risk analysis then it will help to identify the possible risk, issues which will come if development team proceed development with such a poor requirements. Here team will analyze the requirement and try to find out the loop holes in requirement and that can cause problems in futures.