priyanka

• Aug 19th, 2018

Explanation is tooo good thank u soo much

Pradeep Singh

• Jul 1st, 2016

A mistake in coding is called ERROR, Error found by tester is called DEFECT, Defect accepted by developer is called BUG, If build does not meet requirements then it is FAILURE.

Answer Question  Select Best Answer

How the sharepoint application testing will be done, I need detailed analysis how exactly the test team validates the application,what would be the test scenarios,Test coverage points.
if any one has done the SharePoint testing,please provide me the inputs

kavitha

• Dec 21st, 2018

I am new to this. can you please tell what is "restore/import/export site" and managed paths

kavitha

• Dec 21st, 2018

Thanks alot. I have one question here. can you list out one test case on negative scenario?

Answer Question  Select Best Answer

selim

• Sep 14th, 2023

Yes, generally that is how it executed where QA/Tester always assign the priority proportional to severity which has no meaning at all. In the end, dev should decide the priority. Tester assigning the priority has no function at all which makes it a slightly wrong application

bhuvan

• Jun 24th, 2014

Severity will be decided by test end and priority will be decided by dev end in triage call

Answer Question  Select Best Answer

Could please anybody give me the good examples of:

High severity and Low priority
Low severity and High priority
Low severity and Low priority
High severity and High priority
Med severity and Med priority

.... in the terms of functionality.. and Please tell me who will give the priority.

Anjum khan

• Apr 28th, 2024

Severity :- impact of the defect on customer business. Priority:- importance of fixing that defect. High severity and High priority:- login functionality is not working properly . Because i...

shraddha

• Apr 4th, 2018

Logo issue would be high priority and low severity as its not affecting the functionality.

Answer Question  Select Best Answer