What is Boundary value analysis and Equivalence partitioning?

Equivalence Class Partitioning
-This is often used to reduce huge number of test cases to minimal number of them.Basically we divide input data class into three classes

1.Valid input data->For eg:If allowed input for range of numbers is 1 to 100.Then any number between 1-100 is enough rather than executing each of them.

2.Invalid input data below lowest limit->For eg:Lowest limit for range 1 to 100 is 1.So submit data with value less then 1(0,-1 etc)

3.Invalid input data above highest limit->For eg:Highest limit for range 1 to 100 is 100.So input data with value greater then 100(101,102 etc)

Boundary Value Analysis
Problem often occurs at the edges of allowed range.Boundary value analysis helps to find errors are boundaries more than center of data limit.
Three test cases for this ,lets consider for range 1 to 100

1.Test data exactly as the input boundaries of the range.Hence test case is (1,100)
2.Test data below the edges of range.Hence test case is (0,99)
3.Test data above the edges of range.Hence test case is (2,101)

Various bug stages

Bug status varies according to bug tracking tools,but here is the basic stages that a bug undergoes

• New->When bug is newly logged.
• Open->The project manager approves the bug.
  
• Assigned->Project manager assigns the bug to relevant developer.
• Deferred->If the bug is kept to be addressed later.
• Rejected->Developer change the status to rejected if he finds it to be invalid.
• Resolved->When it is fixed by developer.
• Test->It specifies that the bug has been fixed and released to testers.
  
• Reopen->Tester finds that the issue has not been fixed.
• Closed->Tester verifies and find it is resolved.
  

Types of testing

Here is the quick overview of types of testing.

Black box testing-Testing without knowledge of internal structure,code and implementation.

White box testing-Testing with internal logic of application code,structure and implement ion.

Functional testing-Testing features of application,what the system is supposed to do.

Ad-hoc testing-This type of testing is unstructured, takes place without test cases creation

Regression testing-Testing system changes and its effected areas,making sure the functionality which was working earlier has not been disturbed.

Retesting-Simple re-execution of test cases.

Usability testing-Testing how easy to use is the system.

Smoke testing-Testing major functionalities, without paying attention to finer details and is working atleast upto least expected level. It would reveal simple failures severe enough to reject a prospective software release

Performance testing-Check the response time of system.

Stress testing-Testing the system to level it will break.

Load testing-Testing the system response time when it is overloaded with n number of virtual users.

Acceptance testing-Testing done by customer to accept/reject the system and application adheres to requirement or not.

System testing-Testing system as a whole,both functional and non-functional testing takes place.

Unit testing-Testing done by developers for individual modules of system.

Integration testing-Checking module interfaces of system.

Recovery testing-How fast/better system recovers from crashes.

Security testing-Testing unauthorized,unauthenticated access to system

Compatibility testing-Testing compatibility with other systems like OS,browser etc.