Answer:- Scratch org is an expandable Salesforce org that is used for the purpose of testing and development. It is a source-driven and disposable deployment of Salesforce code and metadata. A scratch org is completely configurable, enabling developers to imitate different Salesforce editions that include different features and preferences. The scratch org configuration file can be shared with other team members to carry out development. Additionally, packages can be installed and synthetic or dummy data can be deployed for testing. While its default duration is for seven days, the Scratch org can be created for 30 days after which it is deactivated.

Answer:- The meta configuration file specifies the metadata values to the components. It will result in an error when changes are pushed if there is no configuration file for the component.

Answer:- 1. Javascript establishes HTML properties behavior. 2. If a function, class, and variable defined in the module needs to be imported, the import statement has to be used 3. Javascript files in the LWCs are the ES6 modules and everything declared in the module is local. 4. lwc is the core module in Lightning Web Components. The import statement imports LightningElement from the lwc module.

Answer:- In the Salesforce mobile app or the Lightning component, the force:appHostable interface can be used as a custom tab.

Answer:- The Lightning: action override allows a component to be implemented as an override for a standard action. It is possible to override the New, Tab, Edit, and View standard actions on most standard and custom components. It has no effect except when used within Lightning Experience, the Salesforce mobile app, and Experience Builder sites.

Answer:- 1. Lightning schema builder: It is a UI tool that is used to create and view fields, objects, and relationships 2. Lightning Connect: This integration tool makes it simpler for the Force.com app to consume the data from the external source, which compiles to OData spec 3. Lightning Process Builder: It is a UI tool used for the visualization and creation of automated business processes 4. Lightning Component Framework: It comprises extensions and components that allow the building of recyclable components, personalization of the Salesforce1 mobile app, and development of independent apps 5. Lightning App Builder: It is the latest UI tool that enables quick building of Lightning apps through components given by the Salesforce platform developers

Answer:- The capture phase propagates from top to bottom while the bubble phase propagates from bottom to top.

Answer:- To define the field level security, Lightning:recordEditForm, force: record data, and Lightning: record form should be used.

Answer:- Automation testing is the process of automating the manual testing of the application under test (AUT) or the system under test (SUT). It includes the involvement of testing tools that help us create test scripts, which can be used repeatedly without any human intervention.

Answer:- Selenium RC is called Selenium 2.0, and the integration of Selenium RC and WebDriver as a single tool has formed Selenium 3.0.

Answer:- • Software testing • Known conditions, predefined methods and expected outcome • No need of design knowledge • Finding error or bug • Debugging • Unknown conditions, not preset method and unpredictable outcome • Need full design knowledge • Finding a cause for the error or bug

Answer:- A technique of software testing where the application is tested by ingesting inputs randomly. This test does not follow any pre-defined set of rules. It is carried out to check the behavior of the application.

Answer:- While Baseline testing runs a set of tests to determine the performance, Benchmark testing compares the application performance with industry standards. Baseline testing strives to improve performance with the help of collected information, on the other hand, benchmark testing seeks to improve application performance by matching it with benchmarks.

Answer:- • When a tester finds a bug, the bug is assigned NEW or OPEN with status. • The bug is either assigned to Development Project Managers or is given to Bug Bounty Program. They will check whether it is a valid defect. If not valid, the bug is rejected, and its new status is REJECTED. • Now, the tester checks whether a similar defect was raised earlier. If yes, the defect is assigned a status ‘DUPLICATE’ • Once the bug is fixed, the defect is assigned a status ‘FIXED’ • Next, the tester will re-test the code. In case, the test case passes, the defect is CLOSED • If the test case fails again, the bug is RE-OPENED and assigned to the developer.