is used to inform WebDriver that there could be cases When a page is
loaded by the browser, the elements which we want to interact with may not
load instantaneously. In those cases WebDriver has to continuously listen
to DOM for a given amount of time until either the time expires or the element
In implicit wait, we will actually define a wait time globally, so it is applied to all the elements in the script. Below Implicit Wait() says driver that hey wait for N number of seconds before you throw an error or exception.
Architectures are internet-based systems where the application development does not use the usual server
process. Instead, they rely solely on a combination of third-party
services, client-side logic. Applications are broken up into individual
functions that can be invoked and scaled individually.
Advantage of Serveless Architecture:
Pricing: for years
the cost of provisioning servers and maintaining that 24×7 server team which
blew a hole in your pocket is gone.
It is beneficial
for simple applications with few dependencies
Environments: Setting up
different environments for Serverless is as easy as setting up a single
Defect Triaging is a formal meeting where
all the defects of the current Sprint are discussed and triaged i.e. Prioritized
based on its severity, frequency, risk, etc.
The defect triage meeting discuss about if
defect is valid or user error. If the defect is considered as valid defect then
the next question will be is this defect reproducible? If it is
inconsistent then that will be assigned for thorough analysis. If bug is
reproducible then comes next question is this defect worth of a
fix? i.e., how much it impacts the business of the client. If the impact
is low then it will be deferred to next releases or bug can be closed. If the
impact is high then that will planned for the immediate releases and assigns to
the developer to provide fix with defect status as “Assigned”
If your company is using Trello for project management
Try creating Change Request Flow(plan, protocol). Agree with the client on the steps which are going to happen each time they request a new change. E.g. if they request a new feature, the feature will be included into the next iteration/sprint.
Try to systematise their requests. If they want to add a new button to the existing page, create it as a separate card, not as a comment. If they ask for numerous copy updates, put down these requests to a separate “Copy updates” card.
Non-reproducible bugs – defect has not reproduced on developer pc, i.e a defect coming on your pc does not happen in developer pc’s
Test environment – mismatch of browsers, devices, or configuration of your application with developer.
Duplicate bug – Someone else has already reported the same bug
Misunderstanding the requirements – For any reason, if you did not understand the requirement properly, you would definitely look out for the misinterpreted requirement in actual implementation and when you would not find it, it would be a bug according to you, which will finally get rejected
Change in requirement – When testers are not communicated about requirement changes, more bugs will be reported and ultimately rejected.
Test data used – Test data used for testing was mismatching with a requirement
Improper bug description – If developer does not find proper description and required details in bug report, no matter how critical the bug is, it is expected to be marked as Rejected.