Solved
Cross Browser Testing - CBT Vs Bit Bar
Hello Everyone, In our project we are evaluating how to run web applications across different browsers and mobile devices/OS I have a few questions regarding this and it would be helpful if anyone ...
Forum Discussion
hkim5
Staff
StaffHi Amytav ,
1. We need to run tests locally as access to Excel, Database connectivity is to be maintained during the test run. In this scenario, CBT tool within test complete with the 'Device cloud' add on is the best option?
You would only want to use the Device Cloud add on if you are planning on testing your TC tests across multiple config's of browsers. This is a separate question of whether or not your tests are run locally, as all we are doing is using a remote browser with the Device Cloud add on. Given your example, as long as the data driven loop you created using a locally stored excel spreadsheet is accessible and the location that you made a reference to (with regards to the variable storing the values from the spreadsheet) is still viable, then that data driven loop should keep working, whether you run it locally or against a remote browser.
2. What is the advantage with Bit bar vis-à-vis CBT? We do not have native apps developed on Android/IOS, only web based applications. In this scenario is CBT test tool sufficient to cover all testing possibilities?
They test two different things. Bit Bar is for native mobile applications. So those square icons you see on your smartphone. CBT is for testing the web apps that you would access using the mobile browser on your phone. So if you are trying to functionally test your web application from a safari browser on your iphoneX, it would make sense to use CBT.
3. Are the mobile devices we can select in CBT based on actual device with correct hardware platforms or are these emulators? If they are emulators, how different is CBT from the virtual browser utility?
I am definitely not the best resource on the hardware configs of the device options within CBT, but it's my understanding that this is based on the individual machines. Either way, even if they are emulators, the biggest difference would be that you have access to macOS based browsers, whereas the virtual browser emulators within TestComplete is strictly chrome based.
Hope this helps