Selenium IDE - Inspecting web elements from Local Host Website

In case of Hosted Websites 

when ever we are start recording for testing on particular web page 
automatically steps are create based on selection of the web elements.

In case of non Hosted Websites (Local Host Website)

Only Website is opened but the problem is recording can't recognize the elements so that further commands are not create. 

To over come the above problem we have to change the settings for Selenium IDE plugin as follows

Once we can change the the settings come back to Selenium IDE do the following steps

Jira

JIRA - Agile Management Tool

Agile Scrum Activities

----------------------

Admin

- How to install and Configure

- How create a Project in Jira

- How to add users/people in Jira

Product Owner

- How to create Epic & User   Stories

Srum Master

- Creating Sprint in Jira

- Adding user stories to Sprint

- Starting Sprint

QA and Developer

- Adding sub tasks to Story

- Sprint life cycle in Jira

- Creating bugs in Jira

Test Management Activities

- How to create test cases in Jira   with Zephyr plug-in

- Creating Test Cycles

- Execute/Update Test Cases in Jira

Agile Process

Agile 

• It is process model same as waterfall, spiral etc
• It is an approach to software development under which requirements and solutions eve love through the collaborative effort of self-organizing and cross-functional teams and their customer/end user.
• In this model developer and Testers work together as a team called Agile Team
• 
  
• In this model role is not important the task is most important
• Customer modifications are flexible to implement in this model
• Less documentation, no Functional Requirements Specification

Few terminologies regarding Agile Model

1. EPIC
2. Story
3. Task

In stead of Functional Requirements Specification here we used Epic & Story

Epic is a larger requirement

Story is a smaller requirement

Example:

      Customer create an Epic for using online banking account (larger

      requirement)(Business Needs)

      This larger requirement again divide into multiple stories

           Story 1- as a user login into bank application (Customer Needs)

           Story 2- as a user verify existing balance

           Story 3- as user transferring the amount to another account (Defines                             the solution)

     These are derived from Product Owner 

     Each story can divided into tasks

Developer Task

Review the Story

Estimating the Story(Time)

Design

Code

Unit Testing

QA Task

Review the Story

Preparing test Scenario, Test Cases, Test data, Test Environment

 Execute Test Cases

Report Bugs, etc...