15 January 2018 - naveen automationlabs

Security Testing Test Scenarios – By Naveen AutomationLabs

1. Check for SQL injection attacks

2. Secure pages should use HTTPS protocol

3. Page crash should not reveal application or server info. Error page should be displayed for this

4. Escape special characters in input

5. Error messages should not reveal any sensitive information

6. All credentials should be transferred over an encrypted channel

7. Test password security and password policy enforcement

8. Check application logout functionality

9. Check for Brute Force Attacks

10. Cookie information should be stored in encrypted format only

11. Check session cookie duration and session termination after timeout or logout

11. Session tokens should be transmitted over secured channel

13. Password should not be stored in cookies

14. Test for Denial of Service attacks

15. Test for memory leakage

16. Test unauthorised application access by manipulating variable values in browser address bar

17. Test file extension handing so that exe files are not uploaded and executed on server

18. Sensitive fields like passwords and credit card information should not have auto complete

enabled

19. File upload functionality should use file type restrictions and also anti-virus for scanning uploaded files

20. Check if directory listing is prohibited

21. Password and other sensitive fields should be masked while typing

22. Check if forgot password functionality is secured with features like temporary password expiry after specified hours and security question is asked before changing or requesting new password

23. Verify CAPTCHA functionality

24. Check if important events are logged in log files

25. Check if access privileges are implemented correctly

~~~Subscribe to this channel, and press bell icon to get some interesting videos on Selenium and Automation:

https://www.youtube.com/c/Naveen%20AutomationLabs?sub_confirmation=1

Follow me on my Facebook Page:

https://www.facebook.com/groups/naveenqtpexpert/

Let’s join our Automation community for some amazing knowledge sharing and group discussion:

https://t.me/joinchat/COJqZQ4enmEt4JACKLNLUg

Database Testing Test Cases

1. Check if correct data is getting saved in database upon successful page submit

2. Check values for columns which are not accepting null values

3. Check for data integrity. Data should be stored in single or multiple tables based on design

4. Index names should be given as per the standards e.g. IND_<Tablename>_<ColumnName>

5. Tables should have primary key column

6. Table columns should have description information available (except for audit columns like created date, created by etc.)

7. For every database add/update operation log should be added

8. Required table indexes should be created

9. Check if data is committed to database only when the operation is successfully completed

10. Data should be rolled back in case of failed transactions

11. Database name should be given as per the application type i.e. test, UAT, sandbox, live (though this is not a standard it is helpful for database maintenance)

12. Database logical names should be given according to database name (again this is not standard but helpful for DB maintenance)

13. Stored procedures should not be named with prefix “sp_”

14. Check is values for table audit columns (like createddate, createdby, updatedate, updatedby, isdeleted, deleteddate, deletedby etc.) are populated properly

15. Check if input data is not truncated while saving. Field length shown to user on page and in database schema should be same

16. Check numeric fields with minimum, maximum, and float values

17. Check numeric fields with negative values (for both acceptance and non-acceptance)

18. Check if radio button and dropdown list options are saved correctly in database

19. Check if database fields are designed with correct data type and data length

20. Check if all table constraints like Primary key, Foreign key etc. are implemented correctly

21. Test stored procedures and triggers with sample input data

22. Input field leading and trailing spaces should be truncated before committing data to database

23. Null values should not be allowed for Primary key column

~~~Subscribe to this channel, and press bell icon to get some interesting videos on Selenium and Automation: