Development of School Software

Development of naturalise Softw ar1.0 INTRODUCTIONThis Test Plan has been written to communicate the enlighten easy software development and evidence procedures with the client. It includes the objectives, scope, examination methods, schedule, risks, and approach. This document entrust clearly identify what the try on gestateables exit be and what is deemed in and out of scope.2.0 OBJECTIVES AND TASKSThe School Easy is a school grade and day to day management tool used to let the school and teachers communicate with their students. This software is a tonic product written with Java to be platform independent. The Greater Software is responsible for testing the product and ensuring it meets the clients needs.2.2 TasksThe initial phase of this project will deliver School Easy software with functionality to the client so they can create and store the results from the alpha tests. These result will allow Greater Software to repair the updated versions of the software. The Scho ol Easy must have a full functionality by the delivery date.3.0 SCOPEThe followings are the must have requirements from clients. These and any supplementary point from the client must be all included in the final product.Create initial criteria with detailed sub-steps.Create the transfer schedule.Report and receive feedbacks from the client. appoint transition team.Conduct the tests.Create the final product.Conduct the final test.Deliver the product to the client.First of all, the liaison teacher or account will be appointed to ease the communication between the client and company. She or he will be the main line of communication with the client. The Greater Software will work with School Easy until the client will accept and sign off the final product. Rewriting, moving or porting existing test cases from the existing testing documents is not considered part of this project. Since the client is consisting of three major group of users -teachers, exam departments, and accounts and will probably include students in the future, the Beta testing period will be judge to take much longer than Alpha testing.The Greater Software is committed to delivering the best software to satisfy our clients requirements. In order to sire our pledges, the clients are asked to join our development process from the initial phases of the software development. The following approaches will describe our commitment detailPermit our developers to own and prove the fictional character of our software.Engage our clients by making their feedback process easier and readily accessible to gather early possible feedback data.Conduct testing while enable the larger testing team to track faster, more flexible, and more engaging mixed development environs.These effective testing strategies will include automated, manual, and exploratory tests to reduce risk and slim release cycles. The following tests will be conducted during the developmentUnit tests It validates the smallest regions of the formation, ensuring they handle known input and outputs correctly. It will individually test classes in the finishing to verify they work beneath expected, boundary, and negative cases.Integration tests It exercises an entire subsystem and ensure that a sight of components play nicely together. serviceable tests It verifies end-to-end scenarios that the client will convey in.DefinitionThese tests are basically written and executed by Greater Software to make sure that code meets its design and requirements and behaves as expected. The goal is to discriminate each part of the program and test that the individual parts are working correctly. This means that for any function or procedure when a set of inputs are given then it should return the proper values. It should handle the failures gracefully during the course of execution when any invalid input is given. It also must impart a written contract that the piece of code must assure. It is basically done before integration after Code and Debug development.ParticipantsExaminers, Programmers, TeachersMethodologyThe test will be conducted in the classroom setting while the feedbacks are sent to programmers with error messages.DefinitionSystem Integration Testing(SIT) is a black corner testing technique that evaluates the systems compliance with specified requirements. It is usually performed on a subset of the system while system testing is performed on a complete system and is preceded by the user acceptance test (UAT). It can be performed with minimum usage of testing tools, verified for the interactions exchanged and the behavior of each data knowledge base within the individual stratum is investigated. After the integration, there are three main states of data flowData state within the integration layerData state within the database layerData state within the Application layerParticipantsExaminers, Programmers, TeachersMethodologyProgrammers will write codes according to the specification establ ish by the clients requirements. in that respect are four different system integration test techniquesTop-down Integration TestingBottom-up Integration Testing prepare Integration TestingBig-bang Integration TestingDefinitionPerformance testing, a non-functional testing technique performed to determine the system parameters in terms of responsiveness and perceptual constancy under the various workload. Performance testing measures the quality attri barelyes of the system, such as scalability, reliability and resource usage.Participants Examiners, Programmers, TeachersMethodologyProgrammers will write codes according to the specification schematic by the clients requirements. There are four different Performance Testing TechniquesLoad testing It is the simplest form of testing conducted to understand the behavior of the system under a specific load. Load testing will result in measuring important business critical transactions and load on the database, application server, etc., a re also monitored.Stress testing It is performed to find the upper limit capacity of the system and also to determine how the system performs if the current load goes thoroughly above the expected maximum.Soak testing Soak Testing also known as endurance testing, is performed to determine the system parameters under continuously expected load. During soak tests, the parameters such as memory utilization are monitored to detect memory leaks or other effect issues. The main aim is to discover the systems performance under sustained use.Spike testing Spike testing is performed by increasing the number of users suddenly by a very large sum and measuring the performance of the system. The main aim is to determine whether the system will be able to sustain the workload.DefinitionUser acceptance testing, a testing methodology where the clients involved in testing the product to validate the product against their requirements. It is performed at client location at developers site. UAT is context dependent and the UAT plans are ready based on the requirements and not mandatory to execute all kinds of user acceptance tests and even coordinated and contributed by the testing team.ParticipantsAccountants, Programmers, Students, TeachersMethodologyThe acceptance test cases are executed against the test data or using an acceptance test script and then the results are compared with the expected ones.4.5 mound TestingBatch Testing of the software will be done as needed base.DefinitionRegression testing is the selective retesting of a system or component to verify that modifications have not caused unintended effects and that the system or component still works as specified in the requirements. It makes use of alter tools to control the execution of tests and compares the actual results against the expected result. Usually, regression tests, which are repetitive actions, are automated.Testing Tools not only help to perform regression tests but also helps us to automat e data set up generation, product installation, GUI interaction, defect logging, etc.For automating any application, the following parameters should be considered.Data-driven capabilitiesDebugging and logging capabilities plan independenceExtensibility CustomizabilityE-mail NotificationsVersion control friendlySupport unattended test runsParticipantsAccountants, Examiners, TeachersMethodologyTypically, there are 4 test automation frameworks that are adopted while automating the applications.Data Driven Automation materialKeyword Driven Automation FrameworkModular Automation FrameworkHybrid Automation Framework4.7 Beta TestingDefinitionBeta testing is also known as user testing takes place at the end users site by the end users to validate the usability, functionality, compatibility, and reliability testing. Beta testing adds value to the software development life cycle as it allows the real customer an opportunity to try inputs into the design, functionality, and usability of a p roduct. These inputs are not only critical to the success of the product but also an investment into future products when the gathered data is managed effectively.ParticipantsAccountants, Examiners, Programmers, Students, TeachersMethodologyThere are a number of factors that depends on the success of beta testingTest CostNumber of Test ParticipantsShippingDuration of Testdemographic coverageTask NameStartFinishEffortCommentsTest PlanningReview Requirements documentsCreate initial test estimatesStaff and train unseasoned test resourcesFirst deploy to QA test environmentFunctional testing Iteration 1Iteration 2 deploy to QA test environmentFunctional testing Iteration 2System testingRegression testingUATResolution of final defects and final build testingDeploy to Staging environmentPerformance testingRelease to Production