Microsoft test
A brief description of various tests:
Field editing test. Field editing checks to view formatting, boundaries, and computational errors. If the date needs to be limited to a specific time range, is the software allow input to the date outside of this time? Whether to require a digital field only contain numbers? What happens if the letters will occur? If the calculation is included correctly? Is the field input box to the requested input, is it big enough? If there is a drop box, is it correct?
Stream control and status test. Will the logic reach the expected process after filling in the fields in the form and press the button? Is the value correct when the same page is displayed next time? Sometimes the page first shows the correct value, and will no longer be displayed later; or the opposite.
Configure test. In a feasible case, the application will be tested with as many "supported servers" and client programs.
Load test. Before you test the page or web application as a whole, you should first load and performance testing at the component level to ensure that each portion of the application can run under the appropriate indicator. This isolation test enables the test team more quickly discovered problems using specific technologies. If a small script that performs a database query function is too slow, the component level test is easier to discover it entirely on the entire page or application test.
Regression Testing. After the development department fixes the error in the code, we will re-test to check if the error is fixed and ensures that the repairs do not cause other problems.
A typical plan includes:
Environment simulation information. This document specifies the hardware and software required to set the server and client testing station. This includes operating system versions, application service packages or patches, other desired software (such as SQL Server) version and list of all supported browsers. The test team has a laboratory, a combination of a browser and operating system equipped with a computer running standard, and a combination of not very standard browsers and operating systems.
Basic Testing "standard. This is some basic functions that should be performed before the in-depth test. If the code does not meet these minimum standards, testing is a waste of time. The members of the development member and the test team will agree on the definition of basic test standards in the planning phase of the project.
The list of components and pages to be tested. This list details each DLL, a small script, a filter, and a page. This allows for system testing for each component, and then tests the page.
Test program. These developments are used to mimic the steps that the user usually taken when using tools or pages.
Test Case. Depending on the test scheme, each case contains a series of design steps to test the functionality, stream, status, user interface, and load capability of the page or web application. In the case, you can contain some instructions, such as typing alphanumeric characters in a numeric field, selecting a specific value from the drop-down menu or makes several users simultaneously perform complex table queries.
Test Microsoft Communities To learn how to run, see how our test team evaluates the nearest Microsoft Communities project.
First, the project must meet a series of minimum standards before accepting the project. For Communities, this means that developers must first test some internal version code to be submitted. All known errors must be amended before submitting the code. Then you only need to put the code and release instructions (listed in each internal version), how to install and configure all code and scripts, and all files submitted in each internal version. The list of detail elements is submitted to a specific collection location.
Our test team must first do to make sure all the information provided is correct, and all necessary files exist. Then, install the software on a specially designed system that is very close to the actual environment-tool or page ultimately published web server environment. After that, it is assumed that everything is run in accordance with the expected situation, and a basic test of a series of verified basic functions is performed.
After the project passes the basic test, it began to perform the contents of the test plan. For Communities, this means 22 steps to verify their functions. We push the test message to the newsgroup. If the verification pane can be adjusted, the actual article in the web-based tool is compared to the same newsgroup drawn by another press group client program to ensure that in both The article displayed in the case is the same. See Secret Description 2 About functional test cases. The final step is to perform performance testing to ensure that tools or pages can completely withstand the various traffic on our busy Web site. We use the Microsoft Web Application Stress Tool to simulate a large number of web browser requests with the Microsoft Web Application Stress Tool.
Error screening When the developer submits the code, the test team checks its function, performance, and compatibility with existing software. All errors found will be recorded in our internal error tracking system.
At the end of the test cycle, the development department and test team will discuss these errors together to give each error to each error and a serious level. Developers will solve the problems on the error list and return the revised code to the test team to register. This continuous repeated process will continue until the system is ready, and give it to the publishing team.
In the product delivered to the publishing group, the tester must provide a test summary document, which includes:
Key code of the copy
Records and information related to performance data, allowing the Publishing Group to see what performance should be seen after they start tools or services. If the feeling is running slowly, they can check this information to find out if they are running under the scheduled standard.
The setting description of the environment, including any configuration changes made since the initial test.
List of browsers tested, etc.
Fixed list of all errors
Risks and important lists, which contains a description of any aspects that cannot be tested due to unmovable specific procedures and any unfolded errors
Product installation and use suggestions for this app
Operation Monitoring In front of publishing a complex new web tool, we may put it on the parallel server and invite some Microsoft employees to assist in heavy load tests and integration tests. When it is considered to be applied on the operation server, we will continue to monitor and track errors during its operation. After release, external users can record any questions about our activity tools and pages with Microsoft contact pages and make suggestions. Test team members monitor these reports and assist in debugging and monitoring the active servers. This collaboration implements an accurate test of actual traffic on the server based on actual applications. Most such monitoring includes checking IIS and event logs, and checking the Performance Monitor (which is the information that tracks various IIS statistics applications). See the primary Performance Monitor counter that should be viewed in the auxiliary note 4. For more information on Performance Monitor, see TechNet Articles Monitoring and Optimizing Internet Information Server.
Reuse and automatic operation
Re-use is applicable to code, and it also applies to test plans and solutions. Each new plan is referenced by the previous plan. When the test case can be reused, it will be used directly.
To achieve the best results, remember the following experience:
The test team participated in the initial development process.
Test each component separately before testing the entire tool or page.
Take advantage of the great tools such as IIS Performance Monitor and Web Application Stress Tool.
Assistment Note 1: Microsoft Communities Basic Test
Each of the following should be performed with each supported web browser:
Lord Navigation pane:
Can I move back in the navigation pane on the left, is the pane display correct?
Can I move back in the navigation pane on the left, is the pane display correct? Can I scroll over the area greater than the screen?
Can you choose a different news group, whether the list of article is displayed in the upper right pane?
Can I adjust the left navigation pane and the size of the upper right and lower right pane?
On the right pane:
Does the upper right pane show an article correctly, do you maintain the serial load of each article?
Can I traverse the serial article?
After reading an article, is it marked as red?
If the article list is greater than a page, can you traverse each page in the upper right pane?
Right lower pane:
Can I choose an article and display it in the lower right pane of this page?
Can I release new news, reply group, reply to personal or forwarding articles?
When you reply to your personal or forward messages, whether the default mail client starts and displays new messages?
Can I send an attachment with articles?
Can you view attachments?
Auxiliary Description 2: Microsoft Communities Function Test Case
toolbar:
The verification toolbar is suitable for the page they are located and can be adjusted according to the browser window.
Verify that the local menu can run normally.
Verify the links in the local menu.
Verify that the global menu can run normally.
Verify links in the global menu.
Verify all graphics on the toolbar.
The verification toolbar frame size is not adjustable.
Lord Navigation pane:
Verify that the left pane can be adjusted.
Verify that each group is distinguished according to the name of the newsgroup.
Verify that each group is sorted in alphabetical order.
Verify that you can move back and forth between each group.
Verify that when you click a group, it will be displayed in the article pane.
Compare this list to the groups listed in Outlook Express 5.
Article list pane at the top of the right:
Check Outlook Express 5 and Communities to verify the list of groups of the required groups correctly.
When there is a page, you list each page in the list.
Try all conferences of the session to make sure it contains messages and related to the correct superiors.
Right lower article View pane:
Perform the operation of the publishing and reply group, follow each of the following: Reply and forward:
Use the minimum number of characters in each field.
Use the maximum number of characters in each field.
Use invalid characters in each field.
Verify that the read article is consistent with the same article in Outlook Express 5.
Small script:
Verify the following functions by calling each function with a test script:
GetMessage, GetMessageList, GetMessageAttachment and PostMessage.
Microsoft SQL Server Backend:
Verify that the header is consistent with the header in the NNTP (USENET) server.
Verify that no header is lost.
Verify that the header is copying between the servers.
Auxiliary Description 3: Microsoft Communities Performance Test Case
Test with the minimum supported synchronous connection (1,000).
Test the performance of each small script function:
GetMessage - Based on the size, there is an accessory, there is no accessory, effective message, invalid message (not available message) is tested.
GetMessageList - Based on the list size, existing lists are tested.
GetMessageAttachment - Tests based on small accessories, medium-sized accessories and large accessories.
PostMessage - Tests based on message size and accessory size.
Test the performance of the header transmitted between SQL Server.
Testing from the slave to the master to the other slave unit.
Auxiliary Notes 4: Counters to view when performing performance test
The following is the primary IIS Performance Monitor counter that should be viewed when performing performance testing:
Active Server Page -> Number of requests per second. Tell your server the number of ASP requests processed per second. Active Server Page -> Request to queue. When the server starts receiving loads that exceed its processing power, the request is queued.
Active Server Page -> Request / Rejected. The request will be rejected when the load is receiving the load exceeds its processing capabilities.
Memory -> Available bytes. If the value continues to fall, and the stability can not be reached at any time, memory leaks may occur. When the new page is cached, the available memory will be exhausted, but the drop rate should be stabilized at some time. If you suspect that memory leaks, you should check the number of dedicated bytes of each process to see if it is constantly taking up more memory.
Network Interface -> The total number of bytes per second. This value allows you to know the bandwidth you are using.
Network Interface -> Current Bandwidth. This value tells you the current largest available bandwidth.
Physical Disk -> Current Disk Queue Length. If the disk is a bottleneck, a disk access queuing will occur. Optimizing applications will help with cache feature.
Process -> Special bytes -> InetInfo or DLLHOST or (any process). Pay attention to the process of continuous growth in memory. This value continues to grow indicates that memory leaks occur.
Process -> Processor Time Occupation -> INetInfo or DLLHOST or (any process). This value can show which process takes up the processor's time. Helps to find bottlenecks.
Process -> Thread Count -> InetInfo or DLLHOST or (any process). If there is too much thread, the time occupied by the system between the processes may be more time than the actual processing useful data. This situation is called environmental switching, which is a sign of poor thread performance.
Processor -> Processor Time Occupation. In the case of high load, we believe that 75% of the processor usage is close to the vertex. If you want to run on the usage of this value, there is no space to handle peak traffic or future traffic growth.
System -> Processor Queue Length. When this value is maintained at 3 or 3 or more, it can be explained behind the processor. If you start queuing before reaching the peak load, you should optimize or need to increase processor power.
Web Services -> Current connection. This value displays the current connection number of the web service.
Web Services -> The total number of requests per second. This service tells your part to the total number of HTTP requests to be processed per second. Since all objects in a page (such as graphics, and any independent script or style sheet file) create a separate HTTP request, there is a number of requests for an HTML page. When testing a separate page, the total value of this counter can be used to get the number of pages per second with the number of objects per page.
