Ads

Jira Notes

 Epics:

  1. story with multiple sub stories

  2. this is actually a greater functionality can be subdivided into granular user stories to be actually implemented.

Story:

  1. describe a product feature based on end user perspective

  2. it helps product manager clearly to define the software requirements so the development team understands the desired outcome of the new functionality.

Format:

As a user

i want to

so that

Acceptance critieria:

It determines the completion of the task by having a BDD style feature description

Given that user logging into the application

when the login button clicked

then the user should be navigated to the login page

Product Backlog:

It is a set of well defined requirements/stories.handled by the product owner

Sprint Backlog:

It is a set of well defined requirements that was commited by the developers which will be delivered by the Agile team

Story Points:

effort required to put a product backlog item live.time not equal to effort

Mockup:

visual way of representing a product

Sprint:2 weeks:(time boxed Event)

based on each developers capacity and priority,Stories moved from Product backlog to sprint backlog

then ,sprint will be started by scrum master.then,to in progress,Done we can see the tasks and stories

once sprint completed,we can plan for retrospective ,we have burndown chart,velocity diagram

BurnDown:--->Work decreses gradually

Velocity: commited vs actual

Kanban:

Visualise the work stages

Lead Time:

Time between Task created to work completed

Cycle time:

Time consumed between Work started to work completed

Events:

Daily standup-what u did yesterday,what u work today,any blocker or dependency

Sprint review-before next sprint started,we have to planthe US’s

Story grooming---user story grooming

retrospective---once start doing,stop doing,practise to continue

Comments

Post a Comment

Popular posts from this blog

Rest Assured Api Automation

  1. What is Rest Assured, and why is it used? Answer: Rest Assured is a Java library used for testing RESTful APIs. It simplifies the process of sending HTTP requests, verifying responses, and automating API testing. Rest Assured provides a domain-specific language (DSL) for writing expressive tests, making it easier to test APIs without requiring extensive knowledge of HTTP. GEt method: RestAssured.BaseURI="https://jsonplaceholder.typicode.com/"; RequestSpecification reqSpec=RestAssured.given().accept(Contenttype.json).auth(). basicAuth("username","password").pathParam("sangar","kumar").header("Content-Type","application/json"); Response response=reqSpec.get("/sangar"); sysout(response.asString()); sysout(response.asPrettyString()); Assert.assertEquals(response.statusCode(),200,"Sangar bro"); Assert.assertTrue(response.statusMessage().contains("ok")); Post Method: Response response=Re...
Read more

Appium Notes

Image
  Appium is an open sourced mobile automation tool for testing navitive,hybrid,mobile app and browsers.. Appium internally uses WebDriver json wire protocol(which selenium does) to test the apps. Actually appium server acts as mediator between mobile application and Appium client libraries. Appium Client Libraries code is wrapping as json and sending to the appium server through json wire protocol.--->then appium server sending request to the mobile through UI Automator(kind of engine)--->automator response received by appium server and server sending response to the client libraries   Open image-20240905-071057.png Appium Architecture Appium is an open-source automation tool primarily designed for automating native, hybrid, and mobile web applications on iOS and Android platforms. Here's an overview of its architecture: Appium Server : Appium uses a client-server architecture. It listens for requests from clients (like Selenium WebDriver) and executes the commands on mo...
Read more

Jenkins Notes

  Continuous integration: once new commit is merged to the existing one, existing functionalities should not break.to ensure that for every commit, it is mandentory to run automated test for every new commit. this is called continuous integration.   New Item--->Free style project--->Enter name--->Free style---> General---> Description use custom workspace as project location---> Project is parameterised--->we can set the parameters and can be referred by %value% SourceCode--->Git along with credentials confuigured here--->once push done(this can be achieved by ngrok tunneling tool Build trigger--->usually we mention the schedule time data using cron time to configure automatic run. and we can set chain like depends on other project this will run Build steps-->we can add mvn test like command using windows batch command Post build actions-->we can configure email sending functions
Read more