• LOD is the loss on drying to test as per prescribed conditions which gives loss (presence) of all evaporating solvents along with water.
• LOD test is used to estimate the Water & presented other volatile solvents.LOD is mainly preferable for the material with is Purified by solvents.
• It is the dry base.

• Water content-remove combined form of water.
• Water content gives the moisture present in the sample only.
• Water content is used to estimate the water present in the substance.
• It is unhydrous base.

• Create an ADODB connection object which is required step for connecting to database as below.

Authentication using Id, Password and details.

• • Provider: For SQL server database the provider is “sqloledb”
  • Server: Open the SQL Server in your machine and Right click on the required Database/ click on properties.

• Click on “View connection Properties”

• User Name and Server details are required from this dialogue box

• objConnection.open “provider=sqloledb; Server=SDWA-160-PC; User Id=SDWA-160; Password=; Database=sample; Trusted_Connection=Yes”
• Hence, Connection setup completed and ready for execution.

• Enter the required SQL query to be executed.
• Execution of the query with the statement below.

• The above mentioned sample script has been executed and the value from the database is retrieved.

• Top Command display is the top processes on the system and periodically updates the information.
• Top command displays:
  • Process ID.
  • Username.
  • Priority of Task.
  • Nice value of a task.
  • Amount of virtual memory used by task.
  • Resident size (non swapped physical memory used by task).
  • Amount of shared memory used by task.
  • Process status(whether sleep or running).
  • Share of physical memory usage.
  • CPU time (in Hundredths) and
  • Command or program used or using.

• Joomla is a free and open-source Content Management System (CMS) for distributing web content.
• It is built on a Model-View-Controller (MVC) web application framework that can be used individually, and the CMS that allows to build powerful online applications.
• Joomla is one of the most popular website software’s.
• Joomla is an independent platform, user friendly, extendable, multilingual, accessible, responsive, search engine optimized and so much more.

• CMS is an application (web-based), that provides capabilities for multiple users with different permission levels to manage (all or a section of) content, data or information of a website project, or intranet application.
• Managing content refers to creating, editing, archiving, publishing, collaborating on, reporting, distributing website content, data and information.

• Joomla is used to whole world and millions of websites of all shapes and sizes. Joomla can be used for,
  • Corporate websites or portals, intranets and extranets.
  • Small business websites.
  • Online magazines, newspapers, and publications.
  • E-commerce and online reservations.
  • Government, non-profit and organizational websites.
  • Community-based, school and church websites or portals.
  • Personal or family homepages.

• It is the process of ensure to proper functionality of the graphical user interface (GUI ).
• It may also given by the application and making sure it confirms to its written specifications.
• GUI testing evaluates design elements such as layout, colors, fonts, font sizes, labels, text boxes, text formatting, captions, buttons, lists, icons, links and content.
• GUI testing processes can be either done by the two categories are manual or automatic, and are often performed by third -party companies, rather than developers or end users.
• It can be require a lot of programming and is time consuming whether manual or automatic.
• Usually the software author writes out the intended function of a menu or graphical button.
• GUI testing also tends to test for certain program behaviors that users expect, like an hourglass when the program is busy.

• Manual-based testing.
• Record-reply testing.
• Model-based testing.

• Manual testing is a testing process that is carried out manually in order to find defects without the usage of tools or automation scripting.
• A test plan document is prepared that acts as a guide to the testing process in order to have the complete test coverage.

• In this method, GUI testing can be done using automation tools.
• This is also been divided by the two parts.
• During Record, test steps are captured by the automation tool.
• During playback, the recorded test steps are executed on the Application Under Test.
• Example of tools – QTP.

• In this model, it is a graphical description of a system’s behavior.
• It helps us to understand and predict the system behavior.
• Models help in a generation of efficient test cases using the system.

• Ranorex.
• Selenium.
• QTP.
• Cucumber.
• Silk Test.
• Test Complete.
• Squish GUI Tester.

• Consistency.
• Effectiveness.
• User-Friendliness.
• Functionality.
• Significance

• Software Development Life Cycle (SDLC) is a set of phases that provide a common understanding of the software building process.
• How the software is realized and developed from the business understanding and requirements elicitation phase to convert these business ideas and requirements into functions and features until its usage and operation to achieve the business needs.
• Generally a software engineer should have enough knowledge on how to select the SDLC model based on the project context and the business requirements.
• Therefore, it may be required to choose the right SDLC model according to the specific concerns and requirements of the project to ensure its success.
• You can think of SDLC models as tools that you can use to better deliver your software project. Therefore, knowing and understanding each model and when to use it, the advantages and disadvantages of each one are important to know which one is suitable for the project context.

• There are some various software development life cycle models defined and designed which are followed during the software development process. These models are also referred as Software Development Process Models”.
• Each process model based on a Series of rules unique to its type to ensure success in the process of software development.

• Following are the most important and popular SDLC models followed in the industry & miuns

• • Waterfall Model
  • Iterative Model
  • Spiral Model
  • V-Model
  • Big Bang Model

• The waterfall is a widely accepted SDLC model. In this approach, the whole process of the software development is divided into various phases. In this SDLC model, the outcome of one phase acts as the input for the next phase.
• This SDLC model is documentation-intensive, with earlier phases documenting what need be performed in the subsequent phases.

• The incremental model is not a separate model. It is essentially a series of waterfall cycles.
• The requirements are divided into groups at the start of the project. For each group, the SDLC model is followed to develop software.
• The SDLC process is repeated, with each release adding more functionality until all requirements are met. In this method, every cycle act as the maintenance phase for the previous software release.
• Modification to the incremental model allows development cycles to overlap. After that subsequent cycle may begin before the previous cycle is complete.

• In this type of SDLC model testing and the development, the phase is planned in parallel.
• So, there are verification phases on the side and the validation phase on the other side. V-Model joins by Coding phase.

• Agile methodology is a practice which promotes continue interaction of development and testing during the SDLC process of any project.
• In the Agile method, the entire project is divided into small incremental builds. All of these builds are provided in iterations, and each iteration lasts from one to three weeks.

• Phase 1: Requirement collection and analysis
• Phase 2: Feasibility study
• Phase 3: Design
• Phase 4: Coding
• Phase 5: Testing
• Phase 6: Installation/Deployment
• Phase 7: Maintenance

• The requirement is the first stage in the SDLC process. It is conducted by the senior team members with inputs from all the stakeholders and domain experts in the industry.
• Planning for the quality assurance requirements and recognization of the risks involved is also done at this stage.

• Once the requirement analysis phase is completed the next step is to define and document software needs.
• This process conducted with the help of ‘Software Requirement Specification’ document also known as ‘SRS’ document.

• Economic: Can we complete the project within the budget or not ?
• Legal: Can we handle this project as cyber law and other regulatory framework/compliances.
• Operation feasibility: Can we create operations which is expected by the client ?
• Technical: Need to check whether the current computer system can support the software
• Schedule: Decide that the project can be completed within the given schedule or not.

• In this third phase, the system and software design documents are prepared as per the requirement specification document. This helps define overall system architecture.
• This design phase serves as input for the next phase of the model.There are two kinds of design documents developed in this phase,

• Brief description and name of each module
• An outline about the functionality of every module
• Interface relationship and dependencies between modules
• Database tables identified along with their key elements
• Complete architecture diagrams along with technology details

• Functional logic of the modules
• Database tables, which include type and size
• Complete detail of the interface
• Addresses all types of dependency issues
• Listing of error messages
• Complete input and outputs for every module

• Once the system design phase is over, the next phase is coding. In this phase, developers start build the entire system by writing code using the chosen programming language.
• In the coding phase, tasks are divided into units or modules and assigned to the various developers. It is the longest phase of the Software Development Life Cycle process.
• In this phase, Developer needs to follow certain predefined coding guidelines. They also need to use programming tools like compiler, interpreters, debugger to generate and implement the code.

• Once the software is complete, and it is deployed in the testing environment. The testing team starts testing the functionality of the entire system.
• This is done to verify that the entire application works according to the customer requirement.

• Once the software testing phase is over and no bugs or errors left in the system then the final deployment process starts.
• Based on the feedback given by the project manager, the final software is released and checked for deployment issues if any.

• Bug fixing – bugs are reported because of some scenarios which are not tested at all
• Upgrade – Upgrading the application to the newer versions of the Software
• Enhancement – Adding some new features into the existing software

• Agile testing refers to a software testing practice that follows different principles of agile software development.
• In other words, agile testing means testing software for defects or any other issues quickly or within the context of agile and give quick feedback for better and faster development of the project.

• Testing and development run parallel in agile testing. The tester’s role lies not in identifying defects in the application but in behaving as a developer and bringing in improvements, suggestions, and test cases to be included in the application.
• In agile testing, testers follow the entire lifecycle but due to constant feedback and regular interaction between developers and customers, the application can be delivered in a short time without compromising on the quality.
• The tester and developers respond to quick changes in the application rather than following a fixed plan.

• The principles of agile testing are:

• • Testing is NOT a phase,
  • Everyone participates in the testing process,
  • It shortens the response time of feedback,
  • Reduces test documentation.

• Agile testing requires continuous interaction between developers, customers, managers, stakeholders, and testers.
• Testing is an important component of each phase of the developmental process.

• Unlike the waterfall model, in an agile model, a test plan is written and updated for every release.
• The agile test plan includes types of testing done in that iteration like test data requirements, infrastructure, test environments, and test results.
• Typical test plans in agile includes

• • Testing Scope,
  • New functionalities which are being tested,
  • Level or Types of testing based on the features complexity,
  • Load and Performance Testing,
  • Infrastructure Consideration,
  • Mitigation or Risks Plan,
  • Resourcing,
  • Deliverables and Milestones.

• Agile testing life cycle spans through four stages.

• Software Testing Life Cycle (STLC) is the testing process which is executed in systematic and planned manner.
• In STLC process, different activities are carried out to improve the quality of the product.

• Requirement Analysis
• Test Planning
• Test Case Development
• Environment Setup
• Test Execution
• Test Cycle Closure

• Requirement Analysis is the very first step in Software Testing Life Cycle (STLC). In this step Quality Assurance (QA) team understands the requirement in terms of what we will testing & figure out the testable requirements.
• If any conflict, missing or not understood any requirement, then QA team follow up with the various stakeholders like Business Analyst, System Architecture, Client, Technical Manager/Lead etc., to better understand the detail knowledge of requirement.

• Test Planning is most important phase of Software testing life cycle where all testing strategy is defined.
• This phase also called as Test Strategy phase. In this phase typically Test Manager (or Test Lead based on company to company) involved to determine the effort and cost estimates for entire project.

• The test case development activity is started once the test planning activity is finished.
• This is the phase of STLC where testing team write down the detailed test cases. Along with test cases testing team also prepare the test data if any required for testing.
• Once the test cases are ready then these test cases are reviewed by peer members or QA lead.

• Setting up the test environment is vital part of the STLC. Basically test environment decides on which conditions software is tested.
• This is independent activity and can be started parallel with Test Case Development. In process of setting up testing environment test team is not involved in it.

• Once the preparation of Test Case Development and Test Environment setup is completed then test execution phase can be kicked off.
• In this phase testing team start executing test cases based on prepared test planning & prepared test cases in the prior step.

• Call out the testing team member meeting & evaluate cycle completion criteria based on Test coverage, Quality, Cost, Time, Critical Business Objectives and Software.
• Discuss what all went good, which area needs to be improve & taking the lessons from current STLC as input to upcoming test cycles, which will help to improve bottleneck in the STLC process.

• A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly.
• The process of developing test cases can also help find problems in the requirements or design of an application.

• System testing aims to figure out whether the whole system fulfills the requirements given to it.
• System Test Case will be developed to validate the System as a whole End-to-end, while combining it with the required HW, Database, Networking and any other connections such as Printers, Fax or any other external. Supporting SW application.
• Here, while an input is given to the System, the System’s behavior to handle the input data and its final expected output will be verified.
• System testing take a look at the typical stop product. which includes each unmarried module, interface and every minute details along with all inner and external additives of the system.
• Gadget checking out fundamental reason is to find out whether or not the complete gadget fulfills the requirements as given to it.
• Using tools might be powerful for system testing.
• Device trying out describes how right the product works.

• Functional testing aims to figure out whether given functionality works as specified.
• Functional Test Cases whole be developed to validate the Application according to the functionality demanded by the client or provided in the SRS.
• The input is given to the application, the application behavior to handle the input data and its final expected output will be verified.
• Useful checking out take a look at the functionalities of the product. which incorporates strain, load, safety, overall performance and many others.
• Manual checking out or automation gear may be used for functional checking out.
• Functional checking out describes what the product does.

• Deployment includes all the process required for preparing a software application to run and operate in a specific environment. It involves installation, configuration, testing and making changes to optimize the performance of the software. It can either be carried out manually or through automated systems.
• The advantages of Deployment,
  • Time saving
  • Enhance security
  • Monitor User Actions
  • Effective software updates

• Analog mode records depend on screen as well as followed window.
• It means if you record related to screen then it basically depends on position of the window.
• While recording if you place window somewhere else and while running script you might be moved the window somewhere else. That’s why script is failing.

• Test case is the smallest unit of the testing plan, which includes a description of necessary actions and parameters to achieve and verify the expected behavior of a particular function or the part of the tested software.
• If you have a task to check some functionality, you can create a test script or user story. So, you need to understand where to start testing, which general steps need to be executed and what the result should be And then this scenario is broken down into more detailed parts – test cases – to define all positive, negative, localization and other behaviors of the software.

• The user must be logged.
• Move to the “upload photos” page.
• Click the “upload” button.
• Select photos and Upload them.
• Verify all visitor links.
• Verify all Customer links.
• Verify Customer login with valid data.
• Verify Customer login with invalid data.
• Verify Customer login without data.
• Verify Banker login with valid data.
• Verify Banker login with invalid data.
• Verify Banker login without data.
• Verify Admin login with valid data.
• Verify Admin login with invalid data.
• Verify Admin login without data.
• Verify all Admin home links.
• Verify Admin change password with valid data.
• Verify Admin change password with invalid data.
• Verify Admin change password without data.
• Verify Admin change password with existing data.
• Verify admin logout.
• Create a new user with valid data.
• Create a new user with invalid data.
• Create a new user without data.
• Create a new user with existing branch data.
• Update user with valid data.
• Update user with invalid data.
• Update user without data.
• Update user with existing data.
• Verify that user is able to make financial transactions to added recipient.
• Verify that user is able to add decimal number into amount ( limited by 2 numbers).
• Verify that user is not able to add negative number into amount field.
• Verify that user is allowed to transfer money only if there is proper account balance.
• Verify that there is a confirmation check for financial transactions.
• Verify that user is given an acknowledgment receipt upon successful financial transaction.
• Verify that customer is able to send money to multiple people.

• Let the prime number be n.
• Divide the number n by 1 remainder=0 pass.
• Divide the number n by n remainder=0 pass.
• Divide the number n by 2 remainder!=0 pass.
• Divide the number n by up to n-1 and if remainder not equal zero, then it is a prime number.

• Check whether there is MS office in the system.
• If we open MS word the default page should be blank.
• Check for the Menu options. Whether it has basic functionalities for the file to open, save, save as, edit, copy etc

• Verify the ATM card insertion.
• Verify the ATM card insertion in wrong angle.
• Verify invalid ATM card insertion.
• Verify PIN entry.
• Verify invalid PIN entry.
• Verify invalid PIN entry continually 3 times.
• Verify account type selection.
• Verify invalid account selection.

• Verify there is a train available to the destination.
• Verify the seats are available on the particular date.
• Verify the seats available for required coach that is A/c or Sleeper coaches.

• Click on Start – Program file – MS Office
• Check Ms-Excel in that MS office.
• Check Whether Ms-Excel is opening or not.
• Check the window blank sheet of excel sheet.
• If you close the window asking “are you want save? or not
• If you click ‘yes’ ask where you want save give the path otherwise cancel.

• The web_add_cookie() function adds a new cookie.
• If the name and path match an existing cookie, the existing cookie is overwritten with the new one.
• If the “expires” date has past, the cookie is deleted.

• Issue is nothing but a defect in US terminology, they use issue instead of defect or bug.
• The defect/Bug which is present in the current (release) build, When there is sufficient time to fix the bug, the development team releases the build with bugs.
• These bugs will be mentioned in the release notes as Known bugs. Normally these(bug) issues will be fixed in the future builds or releases.