java - Solution to NB JUnit auto-closing program after 6 minutes -


I am using NJ Junket with Genuine 4, Jelly Tools and Jamie.

Beautiful standard setup in the suite () function after the tutorial available to me. 

  Public Fixed Test Suite () {// Specific Configuration NbModuleSuite.Configuration conf = NbModuleSuite.createConfiguration (Tester Class). Groups (". *") EnableModules ("*."); Conf = conf.addTest ("test1", "test2", "test3"); Return NbModuleSuite.create (conf); }   
 (See if you want more details on the tutorial I have been mentioned)  
 What's happening, this is around 6 minutes mark , Any tester,  
 Before it closes, the tester goes ahead to try and trample on all the ongoing trials.  
 In my case, I am calling  
  new timeout ("Posing", 1000). Sleep ();   
 A little while in the loop, which waits for a certain function call, returns it back. But, about 5:30 in the test, the tester goes beyond this function, eliminates other tests, and closes the window.  
 I am sure that if there is a time limit for each individual exam or if the examiner is completely out of time but I have come to know that if I have stopped for a long time or sufficient random Pushing the clicks and buttons with a few minutes and adding another test or two, the tester still closes for about 6 minutes. The time does not exactly happen at the same time, but it is fine around.  
 I have tried some different ways to stop the examiner, with no fate. And I can not find anything to help online because they are not very publicized. suggestion?   
 
 
 By default, the timeout period must be set to 0L (http: //junit.sourceforge. Net / javadoc / org / junit / test.html # timeout ()) Try to change timeout parameters for a really big value.  
  
 It seems that you have a per-user project property (private properties) or project. You can set the time in the properties file  
  Test.timeout = 3600000   
 Hope that helps!

Comments

Post a Comment