Interview Question


Country: India
Interview Type: Written Test




Comment hidden because of low score. Click to expand.
0
of 0 vote

Here mainly focusing on negative testing
1) without giving any information, click on the submit button
2) Give To and From values in text box, without selecting any date and class, click on the submit button and vice versa(multiple test cases here by filling only one field at a time)
3) select the past date and click on the submit button.
4) No trains between To and From places(invalid To and From values) .
5) If you have train information like which train runs on what day, select those dates and verify no information is displayed.(similar case with class picker)

- Lavanya September 20, 2016 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

1. Past date in DATE field should not be accepted
2. On manually adding DATE, - or . should not be accepted
3. DATE format DD/MM/YYYY or MM/DD/YYYY should not be accepted
4. Special characters other than / should not be accepted
5. In FROM field, Special characters should not be accepted
6. In FROM field, Number 0-9 should not be accepted
7. In FROM field, City name should not start with space.
8. In FROM field, City name should not start with special character.
9. In FROM field, City name should not start with number.
10.In TO field, Special characters should not be accepted
11. In TO field, Number 0-9 should not be accepted
12. In TO field, City name should not start with space.
13. In TO field, City name should not start with number.
14. In DATE field, if the year is non-leap year, then 29th date of February should not be visible in the calendar.
15. In DATE field, if the year is non-leap year, then 29th date of February should not be accepted
manually.
16. IN DATE, for January, not more than 31 as Day should be acceptable.
17. IN DATE, for February, not more than 28 as Day should be acceptable if it is leap year .
18. IN DATE, for February, not more than 28 as Day should be acceptable if it is non-leap year .
19. IN DATE, for March, not more than 31 as Day should be acceptable.
20. IN DATE, for April, not more than 30 as Day should be acceptable.
21. IN DATE, for May, not more than 31 as Day should be acceptable.
22. IN DATE, for June, not more than 30 as Day should be acceptable.
23. IN DATE, for July, not more than 31 as Day should be acceptable.
24. IN DATE, for August, not more than 31 as Day should be acceptable.
25. IN DATE, for September, not more than 30 as Day should be acceptable.
26. IN DATE, for October, not more than 31 as Day should be acceptable.
27. IN DATE, for November, not more than 30 as Day should be acceptable.
28. IN DATE, for December, not more than 31 as Day should be acceptable.
29. IN DATE, for DD should not be accepted as 0.
30. IN DATE, for MM should not be accepted as 0.
31. IN DATE, for YYYY should not be accepted as 0.
32. IN DATE, DD, MM, YYYY should not accept special character and alphabets
33. IN DATE, DD should not be less than 1 or more than 31.
34. IN DATE, MM should not be less than 1 or more than 12.
35. If train is not running on particular day, user should not be able to book the tickets on that particular day.
36. If ticket is already booked from defined Source to defined destination on one day, then for other days those respective
cities should not be shown.
37. If particular CLASS is already selected for FROM and TO City, then another CLASS should not be selected for same Stations.
38. If Clicked On SUBMIT button, then the webpage should not crash.
39. If Clicked On SUBMIT button, then 401 Unauthorized Error should not occur.
40. If Clicked On SUBMIT button, then 500 Internal Server Error should not occur.
41. If Clicked On SUBMIT button, then 404 Content Not Found error should not occur.
42. If any of the field is missing its value, then SUBMIT Button should be disabled.

- IshaJajoo September 11, 2017 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

1. Past date in DATE field should not be accepted
2. On manually adding DATE, - or . should not be accepted
3. DATE format DD/MM/YYYY or MM/DD/YYYY should not be accepted
4. Special characters other than / should not be accepted
5. In FROM field, Special characters should not be accepted
6. In FROM field, Number 0-9 should not be accepted
7. In FROM field, City name should not start with space.
8. In FROM field, City name should not start with special character.
9. In FROM field, City name should not start with number.
10.In TO field, Special characters should not be accepted
11. In TO field, Number 0-9 should not be accepted
12. In TO field, City name should not start with space.
13. In TO field, City name should not start with number.
14. In DATE field, if the year is non-leap year, then 29th date of February should not be visible in the calendar.
15. In DATE field, if the year is non-leap year, then 29th date of February should not be accepted
manually.
16. IN DATE, for January, not more than 31 as Day should be acceptable.
17. IN DATE, for February, not more than 28 as Day should be acceptable if it is leap year .
18. IN DATE, for February, not more than 28 as Day should be acceptable if it is non-leap year .
19. IN DATE, for March, not more than 31 as Day should be acceptable.
20. IN DATE, for April, not more than 30 as Day should be acceptable.
21. IN DATE, for May, not more than 31 as Day should be acceptable.
22. IN DATE, for June, not more than 30 as Day should be acceptable.
23. IN DATE, for July, not more than 31 as Day should be acceptable.
24. IN DATE, for August, not more than 31 as Day should be acceptable.
25. IN DATE, for September, not more than 30 as Day should be acceptable.
26. IN DATE, for October, not more than 31 as Day should be acceptable.
27. IN DATE, for November, not more than 30 as Day should be acceptable.
28. IN DATE, for December, not more than 31 as Day should be acceptable.
29. IN DATE, for DD should not be accepted as 0.
30. IN DATE, for MM should not be accepted as 0.
31. IN DATE, for YYYY should not be accepted as 0.
32. IN DATE, DD, MM, YYYY should not accept special character and alphabets
33. IN DATE, DD should not be less than 1 or more than 31.
34. IN DATE, MM should not be less than 1 or more than 12.
35. If train is not running on particular day, user should not be able to book the tickets on that particular day.
36. If ticket is already booked from defined Source to defined destination on one day, then for other days those respective
cities should not be shown.
37. If particular CLASS is already selected for FROM and TO City, then another CLASS should not be selected for same Stations.
38. If Clicked On SUBMIT button, then the webpage should not crash.
39. If Clicked On SUBMIT button, then 401 Unauthorized Error should not occur.
40. If Clicked On SUBMIT button, then 500 Internal Server Error should not occur.
41. If Clicked On SUBMIT button, then 404 Content Not Found error should not occur.
42. If any of the field is missing its value, then SUBMIT Button should be disabled.

- isha jajoo September 11, 2017 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

1. Past date in DATE field should not be accepted
2. On manually adding DATE, - or . should not be accepted
3. DATE format DD/MM/YYYY or MM/DD/YYYY should not be accepted
4. Special characters other than / should not be accepted
5. In FROM field, Special characters should not be accepted
6. In FROM field, Number 0-9 should not be accepted
7. In FROM field, City name should not start with space.
8. In FROM field, City name should not start with special character.
9. In FROM field, City name should not start with number.
10.In TO field, Special characters should not be accepted
11. In TO field, Number 0-9 should not be accepted
12. In TO field, City name should not start with space.
13. In TO field, City name should not start with number.
14. In DATE field, if the year is non-leap year, then 29th date of February should not be visible in the calendar.
15. In DATE field, if the year is non-leap year, then 29th date of February should not be accepted
manually.
16. IN DATE, for January, not more than 31 as Day should be acceptable.
17. IN DATE, for February, not more than 28 as Day should be acceptable if it is leap year .
18. IN DATE, for February, not more than 28 as Day should be acceptable if it is non-leap year .
19. IN DATE, for March, not more than 31 as Day should be acceptable.
20. IN DATE, for April, not more than 30 as Day should be acceptable.
21. IN DATE, for May, not more than 31 as Day should be acceptable.
22. IN DATE, for June, not more than 30 as Day should be acceptable.
23. IN DATE, for July, not more than 31 as Day should be acceptable.
24. IN DATE, for August, not more than 31 as Day should be acceptable.
25. IN DATE, for September, not more than 30 as Day should be acceptable.
26. IN DATE, for October, not more than 31 as Day should be acceptable.
27. IN DATE, for November, not more than 30 as Day should be acceptable.
28. IN DATE, for December, not more than 31 as Day should be acceptable.
29. IN DATE, for DD should not be accepted as 0.
30. IN DATE, for MM should not be accepted as 0.
31. IN DATE, for YYYY should not be accepted as 0.
32. IN DATE, DD, MM, YYYY should not accept special character and alphabets
33. IN DATE, DD should not be less than 1 or more than 31.
34. IN DATE, MM should not be less than 1 or more than 12.
35. If train is not running on particular day, user should not be able to book the tickets on that particular day.
36. If ticket is already booked from defined Source to defined destination on one day, then for other days those respective
cities should not be shown.
37. If particular CLASS is already selected for FROM and TO City, then another CLASS should not be selected for same Stations.
38. If Clicked On SUBMIT button, then the webpage should not crash.
39. If Clicked On SUBMIT button, then 401 Unauthorized Error should not occur.
40. If Clicked On SUBMIT button, then 500 Internal Server Error should not occur.
41. If Clicked On SUBMIT button, then 404 Content Not Found error should not occur.
42. If any of the field is missing its value, then SUBMIT Button should be disabled.

- isha jajoo September 11, 2017 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

1. Past date in DATE field should not be accepted
2. On manually adding DATE, - or . should not be accepted
3. DATE format DD/MM/YYYY or MM/DD/YYYY should not be accepted
4. Special characters other than / should not be accepted
5. In FROM field, Special characters should not be accepted
6. In FROM field, Number 0-9 should not be accepted
7. In FROM field, City name should not start with space.
8. In FROM field, City name should not start with special character.
9. In FROM field, City name should not start with number.
10.In TO field, Special characters should not be accepted
11. In TO field, Number 0-9 should not be accepted
12. In TO field, City name should not start with space.
13. In TO field, City name should not start with number.
14. In DATE field, if the year is non-leap year, then 29th date of February should not be visible in the calendar.
15. In DATE field, if the year is non-leap year, then 29th date of February should not be accepted
manually.
16. IN DATE, for January, not more than 31 as Day should be acceptable.
17. IN DATE, for February, not more than 28 as Day should be acceptable if it is leap year .
18. IN DATE, for February, not more than 28 as Day should be acceptable if it is non-leap year .
19. IN DATE, for March, not more than 31 as Day should be acceptable.
20. IN DATE, for April, not more than 30 as Day should be acceptable.
21. IN DATE, for May, not more than 31 as Day should be acceptable.
22. IN DATE, for June, not more than 30 as Day should be acceptable.
23. IN DATE, for July, not more than 31 as Day should be acceptable.
24. IN DATE, for August, not more than 31 as Day should be acceptable.
25. IN DATE, for September, not more than 30 as Day should be acceptable.
26. IN DATE, for October, not more than 31 as Day should be acceptable.
27. IN DATE, for November, not more than 30 as Day should be acceptable.
28. IN DATE, for December, not more than 31 as Day should be acceptable.
29. IN DATE, for DD should not be accepted as 0.
30. IN DATE, for MM should not be accepted as 0.
31. IN DATE, for YYYY should not be accepted as 0.
32. IN DATE, DD, MM, YYYY should not accept special character and alphabets
33. IN DATE, DD should not be less than 1 or more than 31.
34. IN DATE, MM should not be less than 1 or more than 12.
35. If train is not running on particular day, user should not be able to book the tickets on that particular day.
36. If ticket is already booked from defined Source to defined destination on one day, then for other days those respective
cities should not be shown.
37. If particular CLASS is already selected for FROM and TO City, then another CLASS should not be selected for same Stations.
38. If Clicked On SUBMIT button, then the webpage should not crash.
39. If Clicked On SUBMIT button, then 401 Unauthorized Error should not occur.
40. If Clicked On SUBMIT button, then 500 Internal Server Error should not occur.
41. If Clicked On SUBMIT button, then 404 Content Not Found error should not occur.
42. If any of the field is missing its value, then SUBMIT Button should be disabled.

- isha jajoo September 11, 2017 | Flag Reply


Add a Comment
Name:

Writing Code? Surround your code with {{{ and }}} to preserve whitespace.

Books

is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.

Learn More

Videos

CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.

Learn More

Resume Review

Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.

Learn More

Mock Interviews

Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.

Learn More