TestNG interview questions

1) What is default priority if it is not set in?

2) What would be happened if there is -ve priority? 

3) Why -ve priority not gets ignored and will be at higher priority? [Lower the number you set, it will be at higher priority and it is by designed]

4) If the test case has the same priority then how would it be executed? [If there are two methods with the same name in a different class then it will take class-wise in alphabetical orders and run sequentially.]

5) What is the difference between Beforeclass and Afterclass?

6) How can we write our own annotation in TestNG? 

7) Have anyone created own customized listener? 

8) How to run 1000 test cases at a time?

9) Can we run testNG.xml via command prompt? 

10) How do you handle exception in testNG?

11) There is N number of TC and few of them TC are failing, then is there any way to handle it apart from iretry listener? 

12) Can we execute selenium code using a batch file which is managed using the cucumber framework?

13) What is the difference between after group and before a group?

14) How to run test cases in parallel using testNG.xml and what will happen when there is parallel execution using the same data provider?

15) How do you manage, if there are multiple threads are running using TestNG and writing data in an excel sheet? 

16) How to run the same test case multiple times?

17) How to do Cross Browser Testing using Selenium WebDriver?

18) How do you execute multiple test cases in a single web driver instance?

Read More

Payment Gateway Testing Checklist and Test Cases

The following checklist can be helpful for testers and could be used as a reference:

1) Set up a payment processor sandbox.

2) Gather test credit card numbers that would be used for testing different credit cards. As an example, such information for the Braintree payment processor can be found at Braintree payments.

3) Verify the behavior of the application when a transaction is successful.

4) After a successful transaction verify if the payment gateway returns to your application to show some kind of successful transaction/confirmation message.

5) Verify that the customer gets some kind of transaction confirmation notification like Order confirmation email, etc. if the transaction is successful.

6) Check what happens if a payment fails or payment processor stops responding- is there any error message?

7) Verify the application behavior with browser popup blocker on and off. This may be helpful if any confirmation messages are being displayed in the popup.

8) Verify different fraud prevention/security settings.

For example, if customer billing information does not match with the address provided to the issuing bank- any mismatch will result in transaction decline.

9) Verify the transaction entries in the database if the tester has access to the Application database.

10) Check what happens when a customer session expires.

11) Check the console during the entire transaction and report any console errors that are observed.

12) Verify that that transaction is done on a secure channel.

For example, the checkout pages may be HTTPS versus the rest of the website that is HTTP pages.

13) Verify that the payment processor currency is set up correctly.

For example, if the application/website is a Canadian company/retailer, the payment processor should be set up to accept CAD currency.

14) If the applications have multiple payment options like Credit card and PayPal together, both payment options need to individually tested from end to end.

15) Verify that refund or void amount (from payment processor admin portal) is the same as the transaction amount. In no case, the refund/void amount should exceed the transaction amount.

Read More

Database Testing Test Cases

1. Check if correct data is getting saved in the 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 a 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 the 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 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. The field length is shown to the 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 the 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 the database

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

Read More

Manual Test Cases for Pen

Installation Testing:

1. Check if all parts of the pen are fitting properly and no loose-fitting. 

2. Check if the pen ball is fitted properly and the ball is moving with ease. 

UI Testing :

3. Check if the dimension of the pen as per mentioned in the requirement. 

4. Size and shape should be confirmable for writing.

5. Logo on the pen should be properly printed.

Usability Testing:

6. Check if the grip on the pen is superior. 

7. Check if the pen is writing smoothly with continuous and not breaking while writing.

8. Check if pen ink is not getting blemish while writing on the paper.

9. Check if the pressure needs to be applied on the pen to write down on the page with least efforts.

10. Check if the pen is usable for similar refills of different brands.

Functional Testing:

11. Check if the pen is writing on the page properly. [

12. Check if the ink on the paper belongs with the similar color as what we see in the refill.

13. Check if written on paper is not getting fade out after some time. If the requirement saying about ink is waterproof then apply water on written text and check the behavior of the ink.

14. Check if the pen is making the width of the line as per the specified millimeter range. If the pen is coming with two different sets of millimeter ranges i.e. 0.5 mm and 0.7 mm then make sure that line width is properly producing by pen as per design. [Validation Testing]

15. Check if the pen is properly working in the flight where different pressure conditions. [Performance testing]

16. Check if the pen is not used for a substantial period of time and check if the ink is not clot inside the pen. Check if the user is able to access the pen with ease. [Recovery testing]

17. Check if the material used to manufacture is safe to use for chewing or kept in mouth. Generally, users are used to putting the pen in the mouth while writing, so make sure that pen is safe to put in mouth or chewing.

18. Check if the ink is not being a leak from refill in normal conditions.

19. Check if the pen is working with different writing angles like the notice is displayed on notice board and user want to write on the notice board.

20. Check if the flow of ink is consistent while writing. The Badly designed pens have a problem with uneven ink flows.

21. Check if the pen ink is not getting dry very quickly or very slowing. While writing on page ink coming out of the pen point, so it should neither dry quickly nor dry too late.

Capability testing

22. Check if the pen is properly working on Space environment if it mentioned in the requirement specifications. 

23. Check if how much longer you can able to write with the single refill of the pen.

24. Check if the pen is properly writing on different type’s surfaces like smooth paper, rough paper, wooden material, plastic, leather, steel, glass, etc.

Robustness Testing

25. Check if the pen is properly gripped on the shirt pocket and user able to carry on the pocket with ease.

26. Check if pen writing point is strong enough to bear a load of different users like some user used to write with some extra pressure on the pen tip.

Negative Test Cases for Pen:

27. Check pen stress testing by dropping pen down from the practical height and check if nothing is breaking, no any damage to pen and pen is working without any issues.

28. Hold the pen upwards direction for some time and try to write on paper.

29. Keep the pen in water and try to write on paper.

30. Check how the pen is working at different climate environmental conditions like at room temperature, different climate conditions.

Read More

Manual Test Cases For ATM Machine

Installation Testing

1. Check if all parts of a machine is fitting properly and no loose fitting properly

2. Check if the keypad is fitted properly on ATM machine

3. Verify the type of ATM machine whether it is card intake machine or card swap machine

4. Check if slots are available for all types of notes (100,500,2000 etc)

UI Testing

1. Check if machine design is as per requirement

2. Check if length, the width of the machine is as per specifications

3. Check if the logo is properly printed on ATM Machine

4. Verify if bank name and logo is placed properly

5. Check if the machine has buttons like Enter, Cancel, Clear, and 0-9 to fill the code

6. Check if ATM have a touch screen or not

Usability Testing

1. Check if the machine is working with minimum noise and if it is smooth or not

2. Check if card insertion slot is as per specifications

3. Check if there is an image or presentation to show how the card can insert from the proper side

4. Check if font available on ATM screen is as per the specifications

5. Verify that ATM screen is smooth and operational

6. Verify that there is an option available for a user to select languages

7. Verify that option available to select account type

Functional Testing

1. Check if all buttons are working properly

2. Check if the machine is asking for a PIN number before displaying card/bank details

3. Check if after filling the correct pin, it display bank account details

4. Check if a user is allowed to check available account balance

5. Check if a user is allowed to enter amount in multiple denominations on the screen like 100,500

6. Check if the user cannot fetch more amount than the total amount available into his account

7. Check if a user is allowed to enter amount again in case it was entered incorrectly

8. Check if a user is not allowed to fetch the amount more than per day transaction limit amount

9. Check if there is an option to print the transaction
10. Check if there is the session is timeout maintained for the user

11. Check if in case sudden power failure in between transaction, the transaction must be marked as null and the amount is not withdrawn from  user's account

12. Check if ATM pin change funtion is working properly or not

13. Check out the total amount in the account after debit or credit

Non Functional Testing

1. Check if the last four digits of account no is visible on printed statement or not

2. Check if a pin must be entered within 15 seconds

3. Check if ATM can be restarted or not when required

4. Verify that the ATM machine is secured enough

5. Check out that the cashbox in ATM can be opened to fill the cash

6. Check out that the inbox of printer can be opened to fill the ink or tonner

7. Check out that the paper of printer can be filled on the printer

Performance and Security Testing

1. Verify that there are a limited number of attempts for the user to enter the pin code

2. Verify that if the total number of incorrect pin attempts then user card must be block

3. Verify that if there is no money in machine then there should be the proper message is displayed

4. Try to enter the wrong pin and check that it is giving an error message or not

5. Verify that account balance is 5000 and user try to fetch 5100 then there must be an alert message

6. Verify that if user card is for saving account and he clicks on a different account like current account then there must be no process

7. Verify that message is receiving on the registered number after withdrawal

8. Check out that user is not allowed to proceed to fetch the money if he has expired ATM card

Negative Test Cases

1. Check how the machine is working at different climate conditions like at room temperature

2. Check if the user is allowed to do transaction after the session timeout for user

3. Check if the user is allowed to do more than one transaction per pin requesting

4. Check if the user fills the wrong pin then ATM is allowed to fetch the money or not

Read More