Software Test Automation FAQ 2

Q.When Automation is not an answer?

Ans :An application is not recommended for automation for the following

• Application is very immature: Application changes frequently in each build.
• Testing Maturity level too low.
• Application flow is not documented properly.
• No testing plan is designed – Not sure that what to test, how to test, what to verify etc.
• No formal test cases are designed.
• Organization can not afford testing budget.
• Importance of testing is very less priority.

Q. What kind of testing methods are possible to test by automated testing?

Ans : Almost all kind of test is possible to execute by automated testing.

• Regression testing
• System and Integration testing
• Smoke Testing
• Multi-Platform testing
• Multi-Language Testing
• Error handling
• Stress Testing
• Load Testing

Q. What is the steps  for development and execute automated software tests?

Ans : For development and execute automated tests the following steps to be consider:

• Requirement gathering, interact with end users
• Requirements study and analysis
• Documentation of all information in proper way
• Design data flow diagram for movement of data and other information as per business requirement
• Design viable function design,interface design specifications if application talk with multiple application
• Consider company budget and schedule requirements
• Define involvement of resources and determine their responsibilities and reporting heads on project
• Document change management process and plan for resolve quickly
• Determine project context, quality of business,scope of testing,approach of testing
• Identify project’s risk factor and more important aspects
• Identify Scope and limitations of testing of the project
• Determine test environments setup in terms of software, hardware,builds and estimate the cost of same
• Determine test methods and approaches(Unit,regression,integration, functional, system, security, load, usability tests etc.)
• select economically viable testware as per business needs (tools, language,test tracking, problem/bug tracking, etc.)
• Determine test input data requirements and define output of result
• Calculate ROI of the project
• Set schedule estimates, time lines, milestones of the project
• Determine, where appropriate, input equivalence classes, boundary value analysis, error classes
• Document test plan and reviewed by experienced tester
• Write test cases
• Setup test environments and testware
• write scripts as per test case
• set up test tracking processes, set up logging and archiving processes
• set up or obtain test input data
• install latest software releases to be tested
• Execute tests
• Evaluate report results as designed test output
• Track bugs and fixes
• Evaluate Retests as needed
• Put value addition if there is a scope
• Maintain ,review and update test plans, test cases, test environment, and testware for project success life cycle

Q. What is test cases and how it help in software testing
Ans : A test case is a document which describes the following in a plan manner

• Input data requirements for the test
• What actions to be perform
• Flow of the software execution correctly
• Expected values of the test
• Verification rule, what to verify and how to verify

A test is identified by unique id no followed by name of the test. As per the Organization and project context test cases may vary.A good test case is a tool for identifying problems of the application.I always recommend to design best of best test cases before development of automated testing scripts.

Q. How is testing affected by object-oriented designs?

Ans : In case of black box testing there is a little difficulty to test for object-oriented design,Because in this types of testing, well understanding of  internal design of the application is very essential.Otherwise, testing is easier to well designed object-oriented application.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.