Selenium "assertChecked" and "assertNotChecked" commands with examples

Selenium  "assertChecked" and "assertNotChecked" commands with examples

assertChecked, assertNotChecked commands are very useful to check whether the check-box or radio button is selected or not.Let's discuss both the commands in detail

assertChecked:

This command is used to check whether check-box or radio button is checked or not, If the check-box or radio button is not selected it will show an error message in the Log

How to use this command in selenium Ide

1) Provide assertchecked in the command field

2) Provide check-box or radio button element locator(css,xpath, id ,name etc..)

3) Click on the play button

If the radio button or check box is selected execution  will be passed, if not execution will be failed and show error message in execution log.

assertNotChecked

This command is opposite to the Assertchecked command, If the check-box or radio button is not selected execution will passed , other wise it will failed and shows error in the execution log.

How to use assertNotChecked  command in selenium Ide

1) Provide assertNotchecked in the command field
2) Provide check-box or radio button element locator(css,xpath, id ,name etc..)
3) Click on the play button

Registration Page for Selenium Practice

Sign Up

1Your basic info

Name: Email: Password: Age: Under 13
13 or older

2Your profile

Biography:

Job Role: Front-End Developer PHP Developer Python Developer Rails Developer Web Designer WordPress Developer Androild Developer iOS Developer Mobile Designer Business Owner Freelancer Secretary Maintenance Interests: Development
Design
Business

Decision Table in Software Testing

It is black-box testing technique, test engineers will use Decision Table  to document the complicated scenarios, the advantage of decision table is it will cover each and every possible conditions and combinations.

Decision table contains two values
1. Conditions
2. Actions

lets discuss decision table with an example.

 In this example i am taking an email login page example for decision table.

 For login to any email application first we need to enter email and password. 

Building decision table for Email and Password

 In the above table "F" indicates the invalid data and "T" indicates the valid data. For the above scenario we have 4 possible conditions .

4 Test cases for above  example: (here iam writing only testcase title)

1.Verify that user should not able to login to the email application with invalid email and invalid password. 
2.Verify that user should not able to login to the email application with valid email and invalid password.
3. Verify that user should not able to login to the email application with invalid email and valid password. 
4. Verify that user should able to login to the email application with valid email and  valid password. 

In the above testcases first 3 test cases are negative testcases and 4th test case is positive test case.

Lets take some complex example.

In this example i am including blank field also, Total 9 combinations are there in this example.
 9 Testcases:
1.Verify that user should not able to login to the email application with blank email and blank password. 
2.Verify that user should not able to login to the email application with blank email and invalid password.
3.Verify that user should not able to login to the email application with blank email and valid password.
4.Verify that user should not able to login to the email application with invalid email and blank password. 
5.Verify that user should not able to login to the email application with invalid email and invalid password. 
6.Verify that user should not able to login to the email application with invalid email and valid password. 
7.Verify that user should not able to login to the email application with valid email and blank password. 
8.Verify that user should not able to login to the email application with valid email and invalid password.  
9.Verify that user should able to login to the email application with valid email and valid password.

In the above test cases First 8 are the negative testcases and 9th test case is positive test case

Tags:

decision table testing example, decision table testing example+istqb, decision table testing,technique+examples,decision table testing simple example, decision table testing questions,decision table testing ppt, decision table testing wiki

Database Testing Interview Questions

1) Write a Query to display maximum salary of an employee from the below table
Table name: employee 

EmpID	Empname	Salary
101	Naveen	30000
102	Saidesh	32400
103	Eshwar	26300
105	leeladhar	86345
106	vijeth	10000

Ans:
syntax: SELECT MAX(column_name) FROM table_name;

Query: SELECT MAX(Salary) FROM employee;
output: 86345

2) Write a Query to update the salary of an employee with 59000 for empid 106

Table name: employee 

EmpID	Empname	Salary
101	Naveen	30000
102	Saidesh	32400
103	Eshwar	26300
105	leeladhar	86345
106	vijeth	10000

Ans: 
Syntax:UPDATE <tablename> SET <column=value>
WHERE <somecolumn=somevalue>;

Query: UPDATE employee SET Salary=59000 where Empid=106;
output:

EmpID	Empname	Salary
101	Naveen	30000
102	Saidesh	32400
103	Eshwar	26300
105	leeladhar	86345
106	vijeth	59000

 

Security Testing in Software Testing

It is a non functional testing , Testers will use the following techniques while doing security testing

1. SQL Injection
2. Cross site scripting
3. URL Manipulation
4. CRLF Injection
5. Password cracking
6. Session Hijacking

ISTQB Latest Dumps

Now a days most of the organizations are conducting a written test for manual testing for freshers and experienced as well.These Questions are very useful for manual testing written test and ISTQB /ASTQB foundation level exam.

ABOUT ISTQB/ASTQB Foundation level exam

1. ISTQB Foundation level exam consists of 40 multiple-choice questions
2.  1 Mark for each question
3.  No negative marks
4.  Pass marks is 26 (65% and above)
5.  Duration of exam : 60 minutes or 75 min(for candidates taking exams that are not in their native or local language)

Test	Questions	Take Test
ISTQB Test 1	10	Start Test
ISTQB Test 2	10	Start Test
ISTQB Test 3	10	Start Test

ISTQB QUIZ 3

1. Evaluating testability of the requirements and system are a part of which phase
Test Analysis and Design
Test Planning and control
Test Implementation and execution
Evaluating exit criteria and reporting

2. Repeated Testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software component
ReTesting
Confirmation Testing
Regression Testing
Negative Testing


3. Impact Analysis helps to decide
How much regression testing should be done
Exit Criteria
How many more test cases need to written
Different Tools to perform Regression Testing


4. Functional system testing is
testing that the system functions with other systems
testing that the components that comprise the system function together
testing the end to end functionality of the system as a whole
testing the system performs functions within specified response times


5. Peer Reviews are also called as
Inspection
Walkthrough
Technical Review
Formal Review

6. The Kick Off phase of a formal review includes the following
Explaining the objective
Fixing defects found typically done by author
Follow up
Individual Meeting preparations


7. Which of the following is not phase of the Fundamental Test Process?
Test Planning and Control
Test implementation and Execution
Requirement Analysis
Evaluating Exit criteria and reporting


8. Which of the following techniques is NOT a black box technique?
State transition testing
LCSAJ (Linear Code Sequence and Jump)
syntax testing
boundary value analysis


9. Success Factors for a review include :
 i. Each Review does not have a predefined objective 
ii. Defects found are welcomed and expressed objectively 
 iii. Management supports a good review process.
 iv. There is an emphasis on learning and process improvement
ii,iii,iv are correct and i is incorrect
iii , i , iv is correct and ii is incorrect
i , iii , iv , ii is incorrect
ii is correct


10. Test Conditions are derived from
Specifications
Test Cases
Test Data
Test Design

Score =
Correct answers:

ISTQB QUIZ 2

1. During the software development process, at what point can the test process start ?
When the design is complete.
When the code is complete.
When the software requirements have been approved.
When the first code module is ready for unit testing
2. In a review meeting a moderator is a person who
Takes minutes of the meeting
Mediates between people
Takes telephone calls
Writes the documents to be reviewed
3. Given the Following program
IF X < Y
THEN Statement 1;
ELSE IF Y >= Z
THEN Statement 2;
END McCabe™ Cyclomatic Complexity is
2
3
5
1
4. How many test cases are necessary to cover all the possible sequences of statements (paths) for the following program fragment? Assume that the two conditions are independent of each other : - if (Condition 1) then statement 1 else statement 2 fi if (Condition 2) then statement 3 fi
2 Test Cases
3 Test Cases
4 Test Cases
Not achievable
5. Acceptance test cases are based on what?
Requirements
Design
Code
Decision table
6. How much testing is enough ?
This question is impossible to answer
This question is easy to answer
The answer depends on the risk for your industry, contract and special requirements
This answer depends on the maturity of your developers
7. A common test technique during component test is:
Statement and branch testing
Usability testing
Security testing
Performance testing
8. Independent Verification & Validation is:
Done by the Developer
Done by the Test Engineers
Done By Management
Done by an Entity Outside the Projects sphere of influence
9. Code Coverage is used as a measure of what ?
Defects
Trends analysis
Test Effectiveness
Time Spent Testing
10. Which of the following uses Impact Analysis most?
Component testing
Non-functional system testing
User acceptance testing
Maintenance testing
Score =
Correct answers:

V Model (Verification and Validation model)

V - Model means verification and validation model . Each phase should be completed before starting the next phase, In this model testing will be done parallel with the corresponding phase of development

Why V model is in "V" shape ?

Validation phase completely depends on the verification phase (Acceptance testing completely depends on BRS, System testing  depends on SRS, Integration testing depends on HLDS, Unit testing depends on LLDS) so we can draw only this diagram in V shape

Verification phase should be carried out from SDLC(software development life cycle) and validation phase should be carried out  from STLC.

V Model starts from the Requirement gathering , Business analyst(BA) gathers all the requirements from the client and prepare BRS(Business Requirements Specification) document. BA will review that document after completion of the requirements gathering, System Analyst will prepare the SRS(System Requirements Specification) based on the BRS, and SA will review that document after completing that document.

Technical architect (TA) will prepare HLDS(High level designs) based on SRS and  TA will review that document after completing that document, Developers will prepare LLDS(Low Level Designs)

and developers will review that LLDS, After that developers will start coding and they will do unit testing with the help of LLDS, after that they will do integration testing with the help of HLDS, after that Testing team will test the application with the help of SRS.
Acceptance testing will be done based on BRS.

Advantages:

--> For  small projects V model is very useful

--> Review activities are performed in each and every stage(ex: BRS, SRS, HLDS, LLDS...etc)

---> Most of the bugs are found early in life cycle.

Selenium Basic Quiz

1. Select the name which is NOT the type of the selenium locaters
Name
ID
Hyperlink
Link Text
2. Select the Browser which is supported by Selenium IDE
IE
Firefox
Chrome
Safari
3. Select the command which is used to print a string value or a variable in Selenium IDE.
Echo
Print
Display
Show

4. select the command which is used to type the text in to text box
Type
Sendkeys
Both
None of the above
5. Select the command which is used to verify radio button selected or check box checked
assertChecked
assertselected
assertcheckbox
assertselect
Score =
Correct answers:

share your score in comments

Agile Testing

Now a days most of the organizations are following agile process for the development of an application. Because It requires very less documentations, stakeholders involved in the daily meetings so it is very easy to get the feed-back from the client(stake-holder).


Benefits of Agile:

--> Agile process saves money and time
--> Requires very less documentation
-->  Regular feed back from the client improves the application quality better.
--> Daily meetings helps to find the issues in advance (causes less cost)

Terminologies Used In Agile process:


Product backlog:

This will help to make the product better. It will contain all the wish list(features)  for product development. 

Below image represents wish list 

Product owner will discuss with customers and users of this product and he will add correct features into product backlog

below image represents final product backlog

Scrum master: Scrum master is like a project manger he is responsible for project progress and coordinating with team members about daily tasks progress, Current sprint progress.

Release backlog:

Finalized features in the product backlog for current release will be added to release backlog 
see below image for release backlog

Prioritization of  Release backlog: 

Based on the importance of the feature from the client side and project side prioritization will be done. below image represents prority of features in product backlog

Estimation of release backlog: 
Estimation of all features in the Release backlog will be done based on the historical data and discussing with subject matter experts to get rough estimation hours for the current release.

Below image represents estimation of release backlog

Sprint:

Sprint will be derived from the prioritized release backlog , Usually big features will be added to 1 sprint, and medium features will be added to sprint 2 and  small features will be added to sprint 3 and sprint  4 for the defects raised in sprint1 testing,sprint2 testing, sprint3 testing.

• Usually duration of sprint size is 14 days (2 weeks) it might be 3 weeks also depends upon project.
• Sprints for current release will be depends upon the features that are added into release backlog.

Image: Features(User stories, requirements) added to sprint

Defect backlog:

Bugs found in the Sprints will be added to the defect backlog and those will be added to the sprint  for developers to fix.

Daily scrum calls(standup-meetings)

Scru master will conduct scrum call every day or weekly twice depends upon project and he will get progress of current sprints(status of developers features development, testers bugs). 

General questions in scrum call from scrum master 

--> What you are going to work on today.?

--> What you have done yesterday?

Burn-down chart:

Burn-down chart represents the status of existing sprint, with the help of this graph we can easily know the status and when we can able to complete the sprint and estimated hours foor sprint. please see the below image 

Must see

V Model

test img