Cross Bridges hiring for QA for their Product based client

Send resume to: venkatesh@crossbridges.co.in

Experience required for the Job: 2 - 5 years

Annual Salary of the Job: 2.00 - 12.00 Lacs

Job Location: Bengaluru/Bangalore

Cross Bridges - A premiere Talent search firm with Pan India reach.

With a deep understanding of the mission-critical needs of corporations, Cross Bridges recognizes the need for agility and influence in the ecosystem to produce results. Our customers often compliment us on our research capabilities and turn- around timelines.

We have an interesting opening for Manual Testing, QA, Linux, Java, Soap professionals with one of our US Based product development clients in Bangalore.

If you are interested in the role, please share your updated CV along with your contact details, so that we can call you back and brief you more on the requirement.

Recruiter

Venkatesh

venkatesh@crossbridges.co.in

PH:9513555477

Read More

Cognizant drive on Oct 19(Bangalore) for Performance Testing

Send resume to: Agisha.K.S@cognizant.com

Immediate job opening for Performance Testing with Cognizant! Bangalore Joining!!

Interview location: Bangalore

Job Location: Bangalore

Available to attend F2F Interview on 19th Oct 19_Saturday: Yes /No   

 Name:

 Contact No:

 Mail ID:

Total years of Experience:

Relevant exp in Performance Testing (Load runner/Jmeter):

Current Company:

Current CTC:

Expected CTC:

Notice Period:

Current Location:

Education: 

Ex-Cognizant Employee: YES/NO

Available to attend F2F Interview on 19th Oct 19_Saturday: Yes /No   

 

Read More

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