A few rules for QAs (Selenium Testers) when testing for story/bug
Don't leave any inquiries unanswered. The acknowledgment criteria must be finished with the end goal to guarantee you completely comprehend what the element/story needs to accomplish.
Ensure you realize how to test the component/story.
Consider the full end-to-end streams when considering experiments.
Consider all related mistake situations, e.g. web benefit association down, invalid data sources, and so forth.
Consider distinctive programs – according to the upheld programs.
Consider versatile effect – portable web and tablet – should any of the highlights carry on diversely when utilized on a touch gadget, contrasted with utilizing a console to explore?
Consider nuts and bolts of security testing, for example, https both URL and assets for ensured zones of the site.
Consider whether this story warrants being incorporated into the mechanization test suite.
As a harsh guide: just situations where its disappointment would result in a P1 or P2 underway will be mechanized. This likewise incorporates situations with a considerable measure of information Selenium Courses in Bangalore to be checked through, which would be extremely redundant to do physically.
When you discover bugs identified with a story, raise them as bug-subtasks, to guarantee the connection to the story is kept.
When marking a story or bug off as testing complete, guarantee a remark is included Jira which incorporates the test condition and code form on which the tests were closed down.
If the story or bug can't, or won't be tried by a QA and will be tried by a designer rather, guarantee you survey the test approach and include a note in Jira that you support of the dev's test approach, in a perfect world with a short depiction. Guarantee the dev includes which variant is being closed down.
On Daily Tasks:-
Understand the territory of the application being changed by engineers
What unit tests have been composed by engineers
What are the high need stories and organize work contingent upon day of dash
Get illuminations on stories that are ambiguous
Review of the robotized verifies whether there were any disappointments
On Sprint Planning:-
Estimate testing for every story
Talk with PO to determine any mistaken assumptions on new stories
Ensure the narratives are testable
Be exceptionally proactive in the gathering by making inquiries to get thoughts for test
Start contemplating abnormal state test situations
On Test Design in a joint effort with Dev and PO:-
Thinking of experiments to approve highlights, applying different test strategies, positive, negative, Boundary Values, Equivalent Partitions, and so forth
Use Mindmaps to help with test situations and client ventures
Consider dangers – give more test conditions around an element of high hazard
Always consider "Imagine a scenario in which", "what else", "by what other means" when planning experiments.
Think about reconciliation tests, how is this component influencing closest neighbor highlights
Really comprehend what is happening while collaborating with an element as opposed to simply taking a gander at if from a surface. Consider what back-end frameworks/DB/Web administrations are being contacted
Candidates for computerization – what test cases are best to be robotized
When there are a considerable measure of blends of information to test, in what manner can the changes be decreased without trading off quality/testing – e.g. utilizing pair-wise test strategy
Peer surveys of test conditions – talking about with engineers what test cases have been planned
On Test Execution/Completion:-
Test Environments/Prerequisite setup before execution
Test when an element is prepared and accessible
Ensure snappy input is given to the designers
Review of the robotized verifies whether there were a disappointments
Does the new created highlight bode well
Talk to designers to enhance testability of an element
Ensure existing tests are refreshed if there is an adjustment in the work process
Maintain the test packs and guarantee all tests are a la mode
On Process Improvement/Self Development:-
Learn about new advancements in programming testing
What are current issues with the QA procedure/How can current issues be comprehended, moved forward.
Discuss with the group their musings about process enhancements
Cooperation of a QA amid prerequisite investigation can help in delivering a far reaching necessity doc with no holes. Portrayal of testing group from the earliest starting point of a task can really connect the prerequisite understanding hole between the undertaking, specialized and business groups.
Like it? Share it!
About the Author
Infocampus HR Joined: December 10th, 2016 Articles Posted: 792
