Scribd
Upload
18 views7 pages

Way To Analyze

The document discusses various negative testing scenarios for applications. It outlines steps to test errors from required fields, data types, field sizes and bounds. It also provides examples to test dates, sessions, performance and overloading the application.

Uploaded by

Marina Ceresau
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
18 views7 pages

Way To Analyze

The document discusses various negative testing scenarios for applications. It outlines steps to test errors from required fields, data types, field sizes and bounds. It also provides examples to test dates, sessions, performance and overloading the application.

Uploaded by

Marina Ceresau
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

First steps:

1. Identificam scopul (pentru ce?)


2. Cum are loc? (functionalitatea)
3. Accepted workflow (accepted scenario)
4. Identificam scenariile negative sau scenariile
care nu sunt luate in consideratie de
BA(business analyst) or dev.
Functionalitatea generala

User1 User2

DB(database)
Or Server

Majoritatea apps unde


participa un user
(comunicarea doar cu
server), extragere info,
cautare s.a
Scenarii negative:
• Fail each step from accepted scenario:
– Embedded Single Quote:
• Most SQL based database systems have issues when users store information that contain a single
quote (e.g. John’s car), try entering text that contains one or more single quotes.
– Required Data Entry
• Test each field on the screen that has been indicated as being required(ce se intimpla daca nu
introduci date)
– Field Type Test
• Your functional specification should clearly indicate fields that require specific data entry
requirements (date fields, numeric fields, phone numbers, zip codes, etc)
– Field Size Test
• Your functional specification should clearly indicate the number of characters you can enter into a
field (for example, the first name must be 50 or less characters).
– Numeric Bounds Test
• if your functional specification requires that a field be in a specific range (e.g. from 10 to 50), you
should try entering 9 or 51, it should fail with a graceful message.

– Numeric Limits Test


• Most database systems and programming languages allow numeric items to be identified as integers
or long integers. Normally, an integer has a range of -32,767 to 32,767 and long integers can range
from -2,147,483,648 to 2,147,483,647. For numeric data entry that do not have specified bounds
limits, work with these limits to ensure that it does not get an numeric overflow error.
Negative scenarios
• Date Bounds Test
– if you are checking a birth date field, it is probably a good bet that the person’s birth
date is no older than 150 years ago.

• Date Validity
– For date fields, it is important to ensure that invalid dates are not allowed (04/31/2007 is
an invalid date). Your test cases should also check for leap years (every 4th and 400th
year is a leap year).

• Web Session Testing


– Most screens in a web application are not designed to be launched without first logging
in. Create test cases to launch web pages within the application without first logging in.
The web application should ensure it has a valid logged in session before rendering
pages within the application.

• Performance Changes
– As you release new versions of your product, you should have a set of performance tests
that you run that identify the speed of your screens (screens that list information,
screens that add/update/delete data, etc).
Negative scenarios(general aproach)

• Block smth if you can (number, input data,


service)
• Make pauses or breaks between steps, like
restart internet connection or smth else.
• Overload the app, max data, max sound etc.
• Use app with same account from different
devices
Links for scenarios:
• https://www.softwaretestinghelp.com/what-is
-negative-testing
/

• https://www.clariontech.com/blog/20-
scenarios-for-testing-login-pages-and-search-
functionality-on-websites
Modalitatea de gindire se obtine prin
experienta, eu nu am gindit asa mereu, feel free
to feel weak, nu exista nimic imposibil, nimic,
totul are solutie, vida, pozitiva, negativa, dar are
solutie !

You might also like