--- old/test/jdk/java/awt/dnd/NoFormatsCrashTest/NoFormatsCrashTest.java	2018-11-26 17:45:21.000000000 -0800
+++ new/test/jdk/java/awt/dnd/NoFormatsCrashTest/NoFormatsCrashTest.java	2018-11-26 17:45:20.000000000 -0800
@@ -22,55 +22,21 @@
  */
 
 /*
-  test
+  @test
+  @key headful
   @bug 4870762
   @summary tests that a drop target JVM doesn't crash if the source doesn't export
            data in native formats.
-  @author das@sparc.spb.su area=dnd
-  @compile NoFormatsCrashTest.java
-  @run applet NoFormatsCrashTest.html
+  @run main NoFormatsCrashTest main
 */
 
-// Note there is no @ in front of test above.  This is so that the
-//  harness will not mistake this file as a test file.  It should
-//  only see the html file as a test file. (the harness runs all
-//  valid test files, so it would run this test twice if this file
-//  were valid as well as the html file.)
-// Also, note the area= after Your Name in the author tag.  Here, you
-//  should put which functional area the test falls in.  See the
-//  AWT-core home page -> test areas and/or -> AWT team  for a list of
-//  areas.
-// Note also the 'NoFormatsCrashTest.html' in the run tag.  This should
-//  be changed to the name of the test.
-
-
-/**
- * NoFormatsCrashTest.java
- *
- * summary: tests that a drop target JVM doesn't crash if the source doesn't export
- *          data in native formats.
- */
-
-import java.applet.Applet;
 import java.awt.*;
 import java.awt.datatransfer.*;
 import java.awt.dnd.*;
 import java.awt.event.*;
 import java.io.*;
 
-
-//Automated tests should run as applet tests if possible because they
-// get their environments cleaned up, including AWT threads, any
-// test created threads, and any system resources used by the test
-// such as file descriptors.  (This is normally not a problem as
-// main tests usually run in a separate VM, however on some platforms
-// such as the Mac, separate VMs are not possible and non-applet
-// tests will cause problems).  Also, you don't have to worry about
-// synchronisation stuff in Applet tests they way you do in main
-// tests...
-
-
-public class NoFormatsCrashTest extends Applet {
+public class NoFormatsCrashTest {
 
     final Frame frame = new Frame();
     private volatile Process process;
@@ -78,6 +44,13 @@
     static final int FRAME_ACTIVATION_TIMEOUT = 2000;
 
     public static void main(String[] args) {
+        if (args.length > 0 && args[0].equals("main")) {
+            NoFormatsCrashTest test = new NoFormatsCrashTest();
+            test.init();
+            test.start();
+            return;
+        }
+
         NoFormatsCrashTest test = new NoFormatsCrashTest();
         test.run(args);
     }