This one pager user story outlines acceptance criteria, technical approach, and testing approach for a new feature to add a location selector. The acceptance criteria define functional requirements like selecting single cities and sorting. The technical approach discusses the Angular implementation. The testing approach covers validating functionality, sorting, caching, and ensuring no performance degradation.
How to deal with bad requirements of softwareBugRaptors
The Software Development Life Cycle (SDLC) starts from requirement gathering and analysis of the requirements. Before freezing requirements a complete analysis is mandatory both by BA and QA team. Always remember, a bad or poorly analyzed requirement can block the road for a good Software Product.
Why You Need to Care About Automated Functional Testing in 2019Sarah Elson
How many times have you come across products that have good UI but really bad functionality such as severe lagging experience and ample number of bugs or vice-versa. There could be multiple reasons for the product to go live, but it definitely gives an indication that thorough testing was not performed. There could be scenarios where a minor software update which was not tested for all the ‘corner scenarios’ could break the existing functionalities in a software product.
10 must do’s for perfect customer experience (Cx) -QualitestQualitest
In an economy where apps have become the very heart and soul of almost any customer centric business, we will not have more than one attempt to ensure the quality of your customer’s digital experience and set a desired customer loyalty.
If we want to the main activities to achieve the above, you might want to look at the below distilled list of must do’s.
User Acceptance Testing- Evaluate Your System's ComplianceBugRaptors
User acceptance testing is the last phase of the software testing process. During UAT, actual users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications. Without proper UAT, changes may appear as though they have been completed. In reality, there might still be work to be done. To know more visit our portfolio www.bugraptors.com
How to deal with bad requirements of softwareBugRaptors
The Software Development Life Cycle (SDLC) starts from requirement gathering and analysis of the requirements. Before freezing requirements a complete analysis is mandatory both by BA and QA team. Always remember, a bad or poorly analyzed requirement can block the road for a good Software Product.
Why You Need to Care About Automated Functional Testing in 2019Sarah Elson
How many times have you come across products that have good UI but really bad functionality such as severe lagging experience and ample number of bugs or vice-versa. There could be multiple reasons for the product to go live, but it definitely gives an indication that thorough testing was not performed. There could be scenarios where a minor software update which was not tested for all the ‘corner scenarios’ could break the existing functionalities in a software product.
10 must do’s for perfect customer experience (Cx) -QualitestQualitest
In an economy where apps have become the very heart and soul of almost any customer centric business, we will not have more than one attempt to ensure the quality of your customer’s digital experience and set a desired customer loyalty.
If we want to the main activities to achieve the above, you might want to look at the below distilled list of must do’s.
User Acceptance Testing- Evaluate Your System's ComplianceBugRaptors
User acceptance testing is the last phase of the software testing process. During UAT, actual users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications. Without proper UAT, changes may appear as though they have been completed. In reality, there might still be work to be done. To know more visit our portfolio www.bugraptors.com
xUnit.js (http://xunitjs.codeplex.com) is a host-agnostic javascript unit test framework that can be run directly from the command line on Linux, Mac, and Windows. Primarily file I/O-based, and requiring neither an HTTP server nor a browser, xUnit.js is a prime candidate for seamless inclusion in build automation systems, continuous integration environments, and even IDEs. xUnit.js encourages developers and quality engineers to follow common testing patterns such as Arrange-Act-Assert, Single-Assert, and Behavior-Naming; and development patterns such as Loose-Coupling, Inversion-Of-Control, Dependency-Injection, and Design-For-Testability. Join us to talk about how to write testable javascript, and how to exercise your javascript APIs and programs cleanly and consistently.
I am Seeking a challenging position in the area of Software Testing in a Professional Organization, where my skills and my education background can add value to the growth of the organization and allow development of my skills to organization potential in the field of Testing.
Superior user experience through cost-effective browser compatibility testing...Mindtree Ltd.
Mindtree helped a global software organization to test the compatibility of their Web browser with thousands of high-traffic websites for a better user experience.
Saksoft Performance Testing offerings for Software products. Our ready to use performance test frameworks identifies the root causes of performance delays and improve the product performance. Tools - HP Loadrunner, Apache JMeter, Shunra
xUnit.js (http://xunitjs.codeplex.com) is a host-agnostic javascript unit test framework that can be run directly from the command line on Linux, Mac, and Windows. Primarily file I/O-based, and requiring neither an HTTP server nor a browser, xUnit.js is a prime candidate for seamless inclusion in build automation systems, continuous integration environments, and even IDEs. xUnit.js encourages developers and quality engineers to follow common testing patterns such as Arrange-Act-Assert, Single-Assert, and Behavior-Naming; and development patterns such as Loose-Coupling, Inversion-Of-Control, Dependency-Injection, and Design-For-Testability. Join us to talk about how to write testable javascript, and how to exercise your javascript APIs and programs cleanly and consistently.
I am Seeking a challenging position in the area of Software Testing in a Professional Organization, where my skills and my education background can add value to the growth of the organization and allow development of my skills to organization potential in the field of Testing.
Superior user experience through cost-effective browser compatibility testing...Mindtree Ltd.
Mindtree helped a global software organization to test the compatibility of their Web browser with thousands of high-traffic websites for a better user experience.
Saksoft Performance Testing offerings for Software products. Our ready to use performance test frameworks identifies the root causes of performance delays and improve the product performance. Tools - HP Loadrunner, Apache JMeter, Shunra
Information Literacy & Open Access for Physics and Astronomy Graduate StudentsJackie Werner
Presented at GaCOMO 2015, Athens, GA
Open access resources are only becoming more prevalent and more integral to doing research; this is especially true for physics faculty, who have been at the forefront of many open access initiatives. Research shows that graduate students tend to pick up their supervising faculty members’ methods of literature searching—but are physics and astronomy graduate students aware of the status of the open access resources they are using? This presentation covers the findings from a survey of physics and astronomy graduate students at two Atlanta universities and its relevance for librarians serving students in the sciences.
Contact me for the PowerPoint file, including a notes section on each slide, or for further information on my research.
En esta presentación podremos observar las características más frecuentes en aquellos jóvenes tecnoadictos y qué pautas se deben llevar a cabo para prevenir dicha adicción.
A practical approach to documentation. A PRD (Product Requirement Document) template for both B2B and B2C products. This works well for startups beyond the early stage of product development and for enterprises creating products.
Everything You Need to Know About Testing Banking Domain Applications.pdfflufftailshop
In the banking industry, consumers increasingly demand digital tools to execute transactions and access services that banks and other financial institutions offer. Ease of use, convenience, personalization, and 24*7 services are among the significant factors driving this consumer demand. In line with this surging demand, organizations compete to deliver the best mobile banking applications and websites that facilitate everything from checking account balances and transferring money to availing loans and trading stocks.
1. One Pager User Story
This method of capturing requirements, technical requirements, functional specifications
and testing methods not only serves the need for documentation. More importantly, this
process brings everyone together to understand the Why, What and How. This does not
only ensure everyone’s on the same page but is also conducive to instant buy-in from the
team which more often than not results to increase in productivity.
Instead of having the BA to write a 30+ page detailed design document where sections in
the document can become out of date by the time the last page is written, write One
Pager User Stories. Store the user stories in ServiceNow the same way BCAA does it
today.
2. Brief summary
User stories are short, simple descriptions of a
feature told from the perspective of the person
who desires the new capability, usually a user or
customer of the system. They typically follow a
simple template:
As a <type of user>, I want <some goal> so that
<some reason>.
3. Acceptance Criteria
Acceptance Criteria are the conditions that a software product must satisfy to be
accepted by a user, customer, or in the case of system level functionality, the
consuming system.
Acceptance Criteria are a set of statements, each with a clear pass/fail result, that
specify both functional and non-functional requirements, and are applicable at the
Epic, Feature, and Story Level. Acceptance criteria constitute our “Definition of
Done”, and by done I mean well done.
We’re not talking about horsheoes here, and there is no partial acceptance: either
the acceptance criteria is met or it is not.
Acceptance Criteria should state intent, but not a solution (e.g., “A user can approve
or reject an invoice” rather than “A user can click a checkbox to approve an invoice”).
4. Technical Approach
With 100% clarity on the acceptance criteria, the Dev team will now answer the
“How” in relation to the implementation strategy? This section should clearly
state how Dev proposes to implement the solution while considering the risks and
benefits. This section can and should state what is not included to better define
the scope and effort.
Example of a benefit would be being able to reuse an existing set of APIs built for
Product A (Web app) when building a new feature in Product B (mobile app).
Technical Approach should address the following concerns:
1) Technical Reviewer – technical viability and elegance
2) Project Manager – relative delivery risks and costs
3) Users/Managers – functionality, user experience, ease of use and training
5. Testing Approach
With 100% clarity on the acceptance criteria and technical approach, the QA
will answer the “How” in relation to how the solution is to be verified and
validated. Also, this section may answer the questions on how defects are to
be tracked and prioritized.
E.g.
1) Perform functionality, integration and system testing
2) Perform boundary testing, input validation and permission based testing
3) Perform back end and front end testing
4) Test lead will create a shared “Outstanding Issues” query on JIRA that will be
shared by all the stakeholders in this project
5) Project Manager will create and main Kanban board specifically for this project
6) Bug Triage is to be held once a week to review defects reported during the
current sprint
9. What QA tested for
OR
How will the BA feel if QA tested for #1?
How does testing for #2 affect the working relationship between Dev and QA?
Is QA really at fault for testing for #2?
10. Here’s an example
As an Agent, I would like to be able to endorse an active policy so I can add assets to the policy
Acceptance Criteria - By product owner
Select one city at a time using the location selector.
- Apply to page X and page Y
- The existing standalone drop down moves into the location selector.
- If viewing multiple cities, select the first city in the location selector.
- If there is a large number of cities, allow the selector to scroll.
- Ensure long city names can fit.
- For very long city names that will not fit the max width of the selector, display with ellipses.
- Default sort: city ascending, province ascending. Case insensitive.
Performance Acceptance Criteria - By product owner
* No performance degradation compared to how page X and page Y were before.
Not included in Acceptance Criteria - By product owner
- Prompt user before changing city when there are changes. etc.
Technical Approach - By Dev
- Section selector will be done as a new widget so it can be re-used in other pages.
- The Angular services that feed data into the location selector require changing.
- It's anticipated that there will be no back-end service change needed.
- The list of cities will be based on the logged in user.
Test Approach - By QA
- Dirty state checking
- Cities and sort order are correct
- Test tracking of selections
- Test with single and multi-city context
- Test around client side caching behavior moving between pages
Performance Test Approach - By QA
* Verify that you're only getting back one city at a time via the browser's network tab
* Test for no degradation compared to page prior to this change.