top 10 bugs

The first realm of testing: perimeterBugTransfer "Consciousness determines action, action determines result" is well known in managementFamous saying. In the past few years, I did not have this awareness and did not take the initiative to think about this problem. However, with the experience of project tasks and a pile of events, this sentence is also suitable for understanding the testing work realm. "Mentality determines fate" and "attitude determines everything". Many famous scholars have

After eight months of practice, I should have a summary to review my practice process. What bothers me most is. Why are there so many bugs in the source I wrote? During my junior summer vacation, I joined Company A with many colleagues. In the popular words, this is a 3 + 1 teaching model, that is, three years of school study, plus one year of company internship, that is, I did not take a four-day lesson, however, I do not think that I have learned le

During the software testing process, different people often test the same project, so repeated bug submission may occur, affecting the entire project and personnel: This wastes the time and effort of testers and affects the testing progress. A waste of time for developers to repeat bugs If a developer calculates performance based on the number of bugs, the relationship between the develop

Collecting bugs Time limit:10000 ms Memory limit:64000 K Total submissions:1244 Accepted:523 Case time limit:2000 ms Special Judge Description Ivan is fond of collecting. unlike other people who collect Post stamps, coins or other material stuff, he collects software bugs. when Ivan gets a new program, he classifies all possible

thoughts when I see the activity "raise a BUG and get a bonus. In general, the new FineReport version will be tested by the test department before it is officially released, and then a small range of users will be selected for trial to ensure stability and then released. Within a short period of time after the release, when the number of users increases, some bugs will emerge. After all, each version update and change is relatively large. But t

Share the experience of my debug 1. Priority to solve those reproducible, reproducible bugs are particularly easy to find, repeated debugging test is good, first put the good solution to kill, so the most time-saving. 2. For some bugs do not have a clue or strange phenomenon do not know where to start, looking for experienced colleagues to ask the idea, because in the development of large systems for man

similar to the previous one in the CLI. But one of the most important changes is that the CLI tool is a bug to fetch information, so the burden on the server, when the bug has hundreds of, and the server connection often error.Therefore, in the online version of this change to every 200 bugs to send a request. This greatly reduces the number of connections, but also makes a lot faster. Makes it possible to support multiple tasks at the same time.Plea

developers submit their work, they can reduce the time that other developers use to detect bugs, and it is often difficult to trace the root cause of the problems caused by these bugs, because the problem is usually due to the integration of new code, Bugs that occur as a result of integration may have been embedded in the code for a long time before a problem o

Problem Description: Some bugs in the test process are considered to be invalid bugs, but from the user's point of view, the test believes that the bug needs to be changed, and then the test is more effective to persuade research and development to modify the bug. Wonderful answer: 1. Reverse the idea of research and development leadership, improve the response speed of researchers: a). Let the leadership o

more information is saved as:#/home/xxx/test/java_test/corefmodule/hs_err_pid2398.log## If you would like to submit a bug report, please V isit:# http://bugreport.java.com/bugreport/crash.jspPossible causes of the problem: Not enough memory--->-xmx2g above Model file not found---> Verify that the model file path exists The model has no write-initialization code---> initializes it when the function executes 2, the phenomenon Description: The program is interrupted, the foll

that the local debug program is not connected to the server side.This machine serves as the service sideYou only need to modify the "Connection Type" as a client compared to the native machine.At this point eclipse will enter the state of waiting for the connectionThe connection program uses the following parameters to connect to the local server, IP address should be replaced by implementing IP ~ ~"-agentlib:jdwp=transport=dt_socket,suspend=y,address=127.0.0.1:8000"F:\study\eclipsepro\screensn

1 、--in the packaging release Springboot, first in the Pom.xml springboot embedded Tomcat removed, so that when packaging will not hit the Tomcat jar packageAs shown below:If you also need inline tomcat, set the Tomcat scope scope to prividedAs shown below:2 、--Pack The Springboot into a war directly after deploying to Tomcat's WebApps, the following problems are encounteredWant to access the project directly through the IP address, but found that the project executed two times in Tomcat boot, t