- What is NOT about Automation Testing? * (Single Choice)
- Automation Testing is a testing process which use automated tools to validate testing output correctly
- Automation Testing is a testing process which use automated tools to validate testing output and manage bugs of software
- Automation Testing is a testing process which use automated tools to prevent software problem
>>>>>>>>=========<<<<<<<<<<<
- What is the right concepts about Automation Testing? * (Single Choice)
- Automation help you have more free time
- Automation is expensive
- Automation is better than manual
- Automation limits human interaction in Software
- Automation reduces effort and increase quality
>>>>>>>>>>========<<<<<<<<<<<<<
- What is xpath statement? * (Single Choice)
- //input[@id='Login']
- [id*='Login']
- html/body/table/tbody/tr[3]/td[2]/span
- count(//td)
>>>>>>>>>>>>>>>=========<<<<<<<<<<<<
- What describes right work flow of browser? * (Single Choice)
- Let us know what kind of dish(es) you'll be bringing
- Browser is a software to storage a website
- Browser is a software to present a website
- Browser is a software to present only html scripts
- Browser is a server to request a website resource to present website content
- Browser is not an interpreter, it just reloads all contents from server resource
>>>>>>>>>>>>>>=========<<<<<<<<<<<<<<
- What is NOT Browser Components? * (Multiple Choice)
- User Interface
- Browser Engine
- Render engine
- HTML and CSS
- Networking
- User Interface back end
- Javascript interpreter
- Data storage
>>>>>>>>>>>>>========<<<<<<<<<<<<
- Automation task includes: * (Multiple Choice)
- Verifying Bug/Defect
- Running Regression Test
- Running Smoke Test
- Making output report
- Verifying Manual Test Cases
- Coding all functions of testing
- Finding solution to increase testing coverage
- Reducing manual mistake
- Reducing manual task
- Replace manual testing
- Training manual tester to automation tester
- Collecting and Researching new technical
>>>>>>>>>>>>>=======<<<<<<<<<<<<<<<
- What does Automation Tester do when test case have some steps can NOT be automated? * (Multiple Choice)
- Passing them to manual team for testing
- Trying to find automated solution
- Ignoring them and continuing next test case
- Inserting manual steps into automation scripts
- Making some tricks to by pass these steps
- Telling to the client
>>>>>>>>>>>>======<<<<<<<<<<<<<<<
- In software testing pyramid, which order should be followed to make a successful project? (Single Choice)
- Unit & component test -> Services test -> UI Automated testing -> Manual test
- Services test -> UI Automated testing -> Manual test -> Unit & component test
- Unit & component test -> Services test -> Manual test -> UI Automated testing
- Unit & component test -> UI Automated testing -> Services test -> Manual test
>>>>>>>>>>>>>>====<<<<<<<<<<<<<<
- When do we decide use automation for testing (Single Choice)
- Software cycle time is longer than balance point in cost comparison chart between Auto vs Manual
- Project has many test cases hard to perform by manually
- Too much test cases in project.
- Automation tool can support technologies are used in product.
>>>>>>>>>>======<<<<<<<<<<<<<<
- What is the first criterion when do we decide selecting an automation tool to our project? (Single Choice)
- Cost
- Scripting language
- Ability to build test framework
- Technologies support
>>>>>>>>>>>>>======<<<<<<<<<<<<<<<<
- Which is correct when talk about table HTML (Single Choice)
- <tr> = row, <th> = header, <td>=cell
- <tr> = row, <th> = hidden row, <td> = table dynamic
- <tr> = row, <th> = header, <tc>=cell
- <tr> = row, <th> = hidden row, <td> = cell