Skip to main content

UAT and Beta Testing



What is the difference b/w UAT and Beta testing?
User Acceptance Testing: Formal testing with respect to the user needs, requirement, Government regulations and business process conducted to determine whether or not a system satisfies the acceptance criteria.
·         It is often the final step before rolling out the application in production environment.
·         This type of testing gives the end users the confidence that the application being delivered to them meets their requirements.
·         This testing also helps nail bugs related to usability of the application.
Beta Testing: is a test process for a computer product prior to commercial release.
·         The software is released to groups of people so that further testing can ensure the product has few faults or bugs and to get the feedback field to a maximal number of future users.
·         It normally can involve sending the product to beta test sites outside the company for real-world exposure or offering the product for a free trial download over the Internet. Example: In web application (Gmail, Orkut, Facebook) released the Beta version
User Acceptance Test (UAT) Planning: It affects the effectiveness of the Testing Process. The Planning process outlines the User Acceptance Testing Strategy. It also describes the key focus areas, entry and exit criteria.
Designing UA Test Cases: derived by various use cases which ensured 100% coverage of all the scenarios during testing and inputs from Business Analysts and Subject Matter Experts are also used for creating
Selecting a Team that would execute the (UAT) Test Cases: Team should have a domain expert so it comprises of in-house team (Developers, Stake Holders, Project Managers, Volunteers, Existing SAM users)
Executing Test Cases: Team executes the Test Cases and may additional perform random Tests relevant to them.
Documenting the Defects found during UAT: Team logs their comments and any defects or issues found during testing.
Resolving the issues/Bug Fixing: The issues/defects found during Testing are discussed with the Stake Holders, Project Team, Subject Matter Experts and Business Analysts. The issues are resolved as per the mutual consensus and to the satisfaction of the end users.
Sign Off: Upon successful completion of the User Acceptance Testing and resolution of the issues the team generally indicates the acceptance of the application. This step is important in commercial software sales. Once the User "Accept" the Software delivered they indicate that the software meets their requirements.
 Who are expert users? Expert users have a stable mental model of the application structure they feel free to explore the application and try new things. They will not be too worried about making mistakes since they feel secure that they will know how to bypass them.
Selecting a Team that would execute the UAT Test Cases is an important step.
·         The UAT Team is generally a good representation of the real world end users and domain expert.
·         The Team thus comprises of the actual end users who will be using the application.
·         The Testing Team executes the Test Cases and may additional perform random Tests relevant to them.
  A company took a contract for developing a navy ship. Who will be responsible for performing UAT before taking the ship on any mission and why? Explain!
Ans. The company in-house teams along with some of the hired domain expert are responsible for the User Acceptance testing. As it designed for navy personnel, so team should include Navy's fleet commanders in chief because they have the broad knowledge from data, navy ships, crews, technical specification, material references that is used. Otherwise, as Navy ship contract is given to third party so some of them from High profile group (Stake Holder) will monitor the UAT and visualize the result thoroughly for making this mission successfully.

Comments

Post a Comment

Popular posts from this blog

Application Lifecycle Management

Application Lifecycle Management Lifecycle the word means “Series of stages through which something passes during its lifetime.” Application lifecycle is similar to giving birth to a young one as per the God’s management. Creating an application is not a big task, but adding the word Management in that Application  Lifecycle is adding a process of distributing with or governing things or people.  When Process comes in a picture, we bound to work according to that, which give the  picture of Application Lifecycle Management. Accumulation process is not that you are bound to move in that particular line only, but it  means you are moving in the correct direction which will give success and 99.9%  assurance that the Project on which you have implemented is having a correct planning,   great controlling, and using the resources in an organized behavior. Application Lifecycle Management is controlling of a software application from planning...
Post a Comment
Read more

What do we mean by Usability?

Many definitions of usability are available, few of them are: 1) In simple words it is "The ease of use". 2) It is the amount of effort required in learning, operating, preparing inputs, and interpreting the outputs of an application. 3) Technical definition prescribed in ISO 9241-11 is: "The extent to which a product can be used by specified users to achieve specified goals with Effectiveness, Efficiency and Satisfaction, in a specified Context of use".  This testing is also called as 'Testing for User-Friendliness'. This testing is done if User Interface of the application stands an important consideration and needs to be specific for the specific type of user. Usability testing is the process of working with end-users directly and indirectly to assess how the user perceives a software package and how they interact with it.    This process will uncover areas of difficulty for users as well as areas of strength. Usability "means...
3 comments
Read more

Project Estimation Template

  Read Me All white cells are editable in the estimation template Estimation Summary 1 In this sheet, mention the basic project information. 2 This sheet gives the amount of effort estimated for each phase, based on the effort distribution. 3 ‘Engineering effort’ is the total amount of effort estimated for the project 4 Total Size (complexity Point) is the calculated value of the complex points or the size of the work that has to be performed. 5 ‘Project Management Effort’ is the percentage of Engineering Effort that will be required for project management. 6 ‘Total Effort (Hours)’ is the sum of ‘Engineering Effort’ and ‘Project Management Effort’ 7 ‘Contingency %’ is the percentage of total effort that counts for an incidental expense 8 ‘Grand Total Effort (Hours)’ is the sum of ‘Total Effort (Hours)’ and ‘‘Contingency %’’ 9 ‘Assumptions’ and Risks: List all the assumptions and risks related to estimation Estimation Criteria 1 Mention the criteria for various complexities i.e. Low...
Post a Comment
Read more