Function Point

Function Point (FP) is an element of software development which helps to approximate the cost of development early in the process. It may measures functionality from user’s point of view.

its technology independent, meaning if you use .Net or Java the function point remains same for all. 

Its doesn't depend on Performance, ex: Fetch report in 2 , 3 or any seconds. 
It does not depend on UI colors, fonts and aesthetic 

Suspension Criteria

Suspension Criteria

Specify the critical suspension criteria for a test. If the suspension criteria are met during testing, the active test cycle will be suspended until the criteria are resolved.

Example: If your team members report that there are 40% of test cases failed, you should suspend testing until the development team fixes all the failed cases.

Test Strategy vs Test Plan

https://www.softwaretestingmaterial.com/test-strategy-vs-test-plan/

https://www.guru99.com/how-to-create-test-strategy-document.html
Download test Strategy document from above website.

Testing Levels: 4 

1. Unit
2. Integration
3. System Testing
4. Acceptance Testing

Test Strategy	Test Plan
Test strategy is a high level document which captures the approach on how we go about testing the product and achieve the goals.	Test Plan doc which contains the plan for all testing activities to be done to deliver a quality product.
Derived from BRD Business requirement document	From SRS document.
Static document. Once defined cannot be changed	Dynamic document, can be changed.
It is defined at organization level	Defined at Particular Project level
Prepared by Project Manager	By Test Lead or Test Manger
Components: ·         Scope and Overview (who will review and approve document) ·         Test Approach (Testing Process, Testing Levels, Roles and Resp of each team member, Types of testing(load, security, Performance Adding new defect, re-testing, Defect Triage, Regression testing & test sign off ) ·         Test Environment ·         Testing Tools (Automation & Test Management tools for execution) ·         Release control ·         Industry standards to follow ·         Risk Analysis ·         Test deliverables ·         Testing Metrics ·         Requirement Traceability Matrix ·         Risk and Mitigation ·         Reporting tool ·         Test Summary	Components: ·         Test plan identifier ·         References ·         Introduction ·         Test Items ·         Features to be tested ·         Features not to be tested ·         Approach ·         Pass/Fail Criteria ·         Suspension Criteria ·         Test Deliverables ·         Testing tasks ·         Environment Needs ·         Responsibilities ·         Staffing and Training needs ·         Schedule ·         Risks and contingencies ·         Approvals

Difference between Test Plan and Test Strategy :BRD vs SRS

https://medium.com/@Techcanvass/are-brd-and-srs-different-or-they-represent-the-same-thing-e9142b1ffbcd

Business requirements are high level description of business needs. The business requirements are written using the customer  perspective.

Ex:
The invoice will be created by the finance manager and will be approved by finance director.

Business requirements document may be prepared by a business analyst even before the project starts.

Intended Audience: Business Analysts, Business users, Project Manager etc. But this document is not prepared for developers/programmers.

System Requirements Specifications document (SRS)

System requirements document (SRS) describes the requirements for the proposed system and it is much more detailed and in-depth document than the BRD. SRS describes the requirements or the features of the software system, which is going to be developed.

The visitor can register as a member by entering the following details:

• Name
• Email ID
• User Name
• Password

The name and email are mandatory fields.

When testing should be stopped, testing exit criteria

https://www.360logica.com/blog/when-should-stop-testing/

Most modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:

• Deadlines (release deadlines, testing deadlines, etc.)
• Test cases completed with certain percentage passed
• Test budget depleted
• Coverage of code/functionality/requirements reaches a specified point
• Bug rate falls below a certain level
• Beta or alpha testing period ends

Exploratory testing vs Adhoc testing

 Exploratory testing:

https://www.guru99.com/exploratory-testing.html

This plays when you do not have supporting use-cases to understand the application. Testers first have to understand the application better and then test the application with formal test approach. 

It is defined as a type of testing where Test cases are not created in advance but testers check system on the fly. They may note down ideas about what to test before test execution. The focus of exploratory testing is more on testing as a "thinking" activity.

Exploratory testing is simultaneous learning, test design, and test execution.

Adhoc testing:

Main aim of Adhoc testing is to find defects by random checking. Adhoc testing can be achieved with the Software testing technique called Error Guessing. Error guessing can be done by the people having enough experience on the system to "guess" the most likely source of errors.

This testing requires no documentation/ planning /process to be followed. 

Since this testing aims at finding defects through random approach, without any documentation, defects will not be mapped to test cases. 

When execute Adhoc Testing?

https://www.guru99.com/adhoc-testing.html

Ad hoc testing can be performed when there is limited time to do elaborative testing. Usually adhoc testing is performed after the formal test execution.

Types of Adhoc testing:

Buddy testing: A dev and QA work together sitting side by side , This testing usually happens after Unit Testing completion.

Pair testing: 

2 testers sit together 90 mins without break. +- 45 mins if required. The testers are Experienced and non-experienced to share their ideas and views

Monkey testing Randomly test the product or application without test cases with a goal to break the system.

Servlets

Reference: https://www.youtube.com/watch?v=7TOmdDJc14s

For a Dynamic web page the request goes to Web Container.  So that request goes to helper application(called as Web Container) . In this Web Container you will be having Servlets.

servlet are basically a java file which can take the request from the client on the internet and it can process that request it can provide you a response in the format of HTML.

Ex: TomCat -- is a Web Container, on the server if you want to achieve dynamic web you need to install TomCat. In TomCat there are 50-60 Servlets. Every request map with one servlet.

Servlet examples:

• Glass fish
• JBoss 
• Websphere