Showing posts with label General Questions. Show all posts
Showing posts with label General Questions. Show all posts

User acceptance testing and test cases

Posted by VIKAS

Q- What's the purpose of acceptance testing? Can we use the same test cases of system testing for acceptance testing?

A- Let's take a look at the first part of the question –"What is the purpose of acceptance testing?" The purpose is to give the end-user a chance to give the development team feed back as to whether or not the software meets their needs. Ultimately, it's the user that needs to be satisfied with the application, not the testers, managers or contract writers.

Which leads us to the second part of the question – "Can we use the same test cases for system testing and acceptance testing." Sometimes Yes and sometimes No
There is a tester put the effort of developing user acceptance test cases.
• Develop the UAT test cases
• Write Test Cases
• Write Test detailed scripts including test data
• Ask Users to check boxes on those scripts as pass or fail

Quality Assurance Testing vs. User Acceptance Testing

Posted by VIKAS

Q-What is the difference between quality assurance testing and user acceptance testing?
QA (Quality Assurance Testing)
  • Technology Oriented Tester
  • Functional Component
  • Integrated features
  • Requirements specification
  • Design Specification
  • Interface level entry points
  • Analysis testing tools
  • UI end to end features
  • Prior to UAT
UAT (user acceptance testing)
  • Business Oriented Testers
  • Business Scenarios
  • Real World business needs
  • UI end to end features
  • Final and Integrated
  • Prior to signoff/prod deployment

How to test software with continuous the changing requirements

Posted by VIKAS

Q- I am a test engineer working on Windows applications. I do manual testing. In the agile world, when things keep on changing every now and then, it's difficult to get well-defined requirement specifications from developers, which disturb test case writing, traceability, and test execution. What would be the right strategy to make sure we are delivering quality product?
If you have dynamic requirements to test software then do follow the below steps:
  • Make it your plan as per list of goals
  • No need to keep actual steps in you plan
  • No need to write every requirement in your planed document
  • Write requirement to help keep everything straight
  • Summarize a group of requirements with a simple sentence
  • Plan should not be documented as huge
  • If the requirement changed during executing test then change it into your document
  • If original requirement changed during executing test then stop testing and make new document
  • Ensure that application or module is stable then update the main document (test case & traceability) and execute updated test cases and finally the sign off the document
The impact of changing requirements is greatly reduced by using this method

VOIP (Voice over Internet Protocol) Testing

Posted by VIKAS

By VOIP if you mean "Voice over Internet Protocol" then VOIP is a protocol optimized for the transmission of voice through the Internet or other packet switched networks. Then testing will be carried out to check
- How the Voice is transmitted through the Internet for its clarity.
- For its features such as forwarding, automatic redial, and caller ID.
- For the ability to transmit more than one telephone call using the broadband-connected
telephone line
- For the Secure calls using standardized protocols here the testing will be to check how the call to encrypt and authenticate the existing data stream.