log.info("Step:Click 'Add keyword' button in Keyword editor window. [Class#Method]");
21. JavaDoc for each method and whole class
/** * Class name and description * * @author * @version 1.0 * @since 26/12/2019 */
/** * Select Record in Table using row_id * * @param row_id - row id of the required row to select * @param columnName - column name * @throws FrameworkException */
22. Fluent builder pattern in each method: Return type is always class name
23. Configurations in environment.xml file
* Manage project configurations under **```environment.xml```** file, > - ```<embedded-mode></embedded-mode>``` **```: If 'ON' test project will support chromium emmberdard mode, if 'OFF' test project only support swing gui mode or pure web```** > - ```<app-mode></app-mode>``` **```: If 'GUI' test project support for pure swing or chrommium emmberdard mode, if 'WEB' test project support only for pure web application```** > - ```<dashboard>OFF</dashboard>``` **```: If 'OFF' while during the execution listeners will disable and not collect execution results for dashboard```**
24. chrome driver is located under the resources folder
25. log4j.xml file is located in the resources folder
26. Data input files like images and pdf are located in the resources folder
1. What are the phrases in SDLC? Requirement analysis Design Development Review Testing Integration 2. Why SDLC is important? It provides a basis for project planning, scheduling and estimating It provides a framework for a set of activities and deliverables It is a mechanism for project tracking and control It increases the visibility of project status to all the stakeholders It helps to identify project risks beforehand 3. What are the QA responsibilities in each SDLC phrase? Requirement analysis : Understand each requirement clearly and clarify when needed. Prepare traceability matrix for test case and requirement mapping Design: Comes up with Test strategy, what to test and how to test Development: Set up test environment and prepare test case documentation Review: Understand what has changed what was done by the developer and what impact, check whether there is UT, IT coverage and decide what remains to automate. Testing: Perform functional, and non-functional testi...
In the Team CI Environment, the scripts are successful one day. the other day it was failing. The next day it is successful. What can be the reason? It can be an issue specific to the relevant machine like a Windows update pop-up or some kind of notification showing up Network issue Server down Browser issue Resource issues like memory, CPU, disk space Users are already logged in to the system Existing live sessions are there The regression suite is failing. How do we highlight it during the daily scrum? when giving updates mention failures Mention the investigation results Highlight the risk of failing and the urgency of fixing them immediately Ask to flag the current working issue and take a new task to the sprint as unplanned Another QA member is on sick leave. Tomorrow is release day. How do you handle the situation? Inform the situation to the scrum master Ask someone to help with the testing Create multiple environments and run automation scripts in parallel Inform abo...
What are the areas that need to be focused on when testing a story? Affected functional areas Technical Impact The fix going to make Dependency functional areas Database related changes Impact on the existing data Different resolutions Different languages Impact for printing Impact on Data Mining Backward Compatibility test Performance test User documents updation Issues reported UI changes
Comments
Post a Comment