SandeepQA

 Profile Answers by SandeepQA 

• Aug 6th, 2015

 

If no any requirement then we must knowledge for domain and as per your experience for that domain.

singla.kaajal

 Profile Answers by singla.kaajal 

• Aug 10th, 2015

 

1.Look and feel(cosmetic like colors,logos,grammer spelling,if frames bleed into one another,content doesnt overlap)
2.Functionality
3.Navigation
4.Negative Testing
5.Focus Testing
6.Form validation testing

Amit Sachdeva

• Aug 22nd, 2015

 

Functional, Negative, Security(if secured site), Performance(for banking and e comm sites), UI, Accessibility, Installation(if product based), Compatibiility and integration tests

Imran Bojagar

• Sep 15th, 2015

 

If we don't have any specific requirement document, that time
1. We have to refer previous versions screen shots, videos and wire frame
2. If BA or Developer is working around the tested then do the conversation with them and try to understand the application.
3. If option 1 and option 2 is not available that time we need to exploratory testing, that gives your the basic idea about application meanwhile doing the exploratory testing we can prepared your test cases. We can user our experience to do testing.

Aruna

• Oct 14th, 2015

 

In such cases when we dont have the requirement document, We have to start the testing using prior experience by doing the exploratory testing.
And one more method is adhoc testing without having any formal document just going thru the pages and menus and trying to find out the flow.
The checklist is:
1. Pages
2. Menus and submenus
3. Links
4. Buttons
5. Social network links if any
6. Video links
7. Corrrect page is rendering or not.
8. content of the page