Software Testing Material

MANUAL TESTING CONCEPTS Introduction to Software Testing ü   What is software Testing ü   Why Software Testing ü   Benefits of Software Testing ü   Who will do the Software Testing ü   What is Quality ü   What is Defect ü   Project Vs Product   Software Development Life Cycle (SDLC) ü   What is Software Development Life Cycle ü   Why Software Development Life Cycle ü   Phases of Software Development Life Cycle ü   Initial ü   Analysis ü   Design ü   Coding ü   Testing ü   Delivery & Maintenance Software Development Life Cycle (SDLC ) Models ü   Water fall model ü   Vmodel ü   Prototype Model ü   Agile Model with Scrum Method  Software Testing Methodologies ü   Block box Testing ü   What is Block Box Testing ü   Who will Perform Block Box Testing ü   How to Perform Block Box Testing ü ...

ONLINE TRICENTIS TOSCA AUTOMATION TRAINING WITH REAL TIME SCENARIOS TOSCA COURSE CONTENT (40 Hours) Tosca has become an leading Automation tool in market migrating most of the existing projects to tosca, which has an excellent flexibility to handle script-free automation tool. This training helps the team to write complex/simple automation scripts very easily and can able to handle any type of scenarios. Here with providing the list of topics covered under this course: Tosca Introduction  (Duration 2 Hours) Brief about Tricentis Tosca Testsuite Overview and concept Business dynamic TestCases and test automation System Requirements for Tricentis Tosca Testsuite Installing Tosca Installation process Unattended installation  License administration Node Locked License Floating License Commuter License Cloud License Specific License Files and directories Maintaining the Tosca installation (Duration 2 Hours) Working Features in TOSCA The Men...

We can perform regression testing Save time by executing the test cases without manual effort. We can reduce the cost to the Company We can maintain accuracy by repeating the tasks in the same manner We can identify bugs We can report the bugs to the developer and the Manager We can ensure quality

XPATH FUNCTIONS IN SELENIUM WEBDRIVER XPath:   //button[starts-with(@id, 'continue')]  XPath: //input[contains(@class, 'suggest')]. XPath : //input[@id='email']/parent::* XPath: //input[@id='email']/following::* XPath: //input[@id='email']/following::tr XPath: //select[@id='month']/following-sibling::* XPath: //select[@id='month']/following-sibling::select/ XPath: //input[@id='pass']/preceding::tr XPath: //select[@id='day']/preceding-sibling::select/ XPath://select[@id='day']/preceding-sibling::* //*[contains(@id,’your-common-pattern’)] Using CSS  we can use as below: With ID - css=input#email or css=#email With Name - css=input[name=email] or css=[name=email] xpath : - //*[@id='email' or @name='email'] xpath: //input[@name='email'][@style='background-color: transparent;'] Some MoreExamples using Xpath Functions:   I often use "contains...

Use at most one action on the screen that is highlighted as the most likely for the user. (Example: in iOS a blue button represents the default or most likely action). To keep controls as unobtrusive as possible for instance by fading them out if they are not used for a while. Make it possible for users to go back to a previous screen for instance by adding a back or cancel button the main function of the app should be apparent immediately. It should speak for itself. If the app is stopped at an unexpected time, user data should be saved locally and available at start-up. Do not use standard buttons for other functions then that they are normally used for

Before your product goes in front of customers, you naturally want to get it tested by the largest number of testers available. This is usually accomplished via alpha builds, closed-beta tests, etc. Developing and testing for the iPhone is a completely different experience altogether, and present these 2 issues to software developers. 1. Lack of testing devices internally. While some of us live in cities where seemingly everyone has an iPhone, the fact is most software testing teams are not fully equipped with iOS devices. To make matters worse, every year one or two new products arrive in the iOS family that require significant capital investments for the team. 2. Difficulty in getting testing devices externally before release. Unless your intended audience is the jail-broken segment, your software product is being developed for a highly controlled environment – iTunes App Store. Just getting your devices properly provisioned internally is difficult enough, getting you...

A very good and important point. Right? If you are a software tester or a QA engineer then you must be thinking every minute to find a bug in an application. And you should be! I think finding a blocker bug like any system crash is often rewarding! No I don’t think like that. You should try to find out the bugs that are most difficult to find and those always misleads users. Finding such a subtle bugs is most challenging work and it gives you satisfaction of your work. Also it should be rewarded by seniors. I will share my experience of one such subtle bug that was not only difficult to catch but was difficult to reproduce also. I was testing one module from my search engine project. I do most of the activities of this project manually as it is a bit complex to automate. That module consist of traffic and revenue stats of different affiliates and advertisers. So testing such a reports is always a difficult task. When I tested this report it was showing the data accurately p...