Welcome to Selenium Scribbles!
Hello and welcome to Selenium Scribbles, your go-to resource for everything related to Selenium! Whether you're a seasoned QA professional or just getting started with automated testing, you've come to the right place.
Here, you'll find a treasure of tips, tutorials, and best practices designed to help you master Selenium and take your automation skills to the next level. From beginner basics to advanced techniques, we cover it all with clear explanations and hands-on examples.
Feel free to explore our posts, leave comments, and share your own insights. If you have any questions or need specific guidance, don't hesitate to reach out.
Happy testing, and here's to your journey with Selenium!
attending grooming sessions, understanding user stories, identifying if there are any gaps in requirements and making them fixed, preparing test cases and in parallel preparing test scripts for previous sprint, executing test cases and running test scripts in CT pipeline on new build.. raising the bugs if there are any failures and tracking them until they got fixed.
along with manual and automation i am having good experience in DB testing like validating table structure for data type, data width, primary keys, foreign keys, constraints, null not null values comparing with UI
apart from that my day to day activities includes attending sprint planning, daily scrum call and sprint
review meeting, demoing user stories, monitoring smoke suites and regression suites in CT pipeline.
if there are any failures fixing the issues.
and also updating regression test scripts if there are any changes in requirements then reviewing those test cases and scripts
DB Migration
pre migration - data backup, data requirements in both db's, mapping the data in source and target db's
-coulum names(Data of Birth, DOB), column data(Male, M), null values in both source and target
consistency between UI and DB (extra columns, removed columns)
ETL and Migration -
post migration - mapping between source and target
SQL with CASE
SELECT OrderID, Quantity,
CASE
WHEN Quantity > 30 THEN 'The quantity is greater than 30'
WHEN Quantity = 30 THEN 'The quantity is 30'
ELSE 'The quantity is under 30'
END AS QuantityText
FROM OrderDetails;
Comparing all data in both tables and to find extra and redundant rows - using EXCEPT and MINUS
