Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for testMod (0.67 sec)

  1. src/test/java/org/codelibs/fess/thumbnail/impl/CommandGeneratorTest.java

                assertTrue(generator.generate("test_id", outputFile));
            } finally {
                outputFile.delete();
            }
        }
    
        public void test_generate_outputFile_null() throws Exception {
            generator.setCommandList(Collections.singletonList("echo test"));
            try {
                generator.generate("test_id", null);
                fail("Should throw exception for null output file");
    Registered: Thu Sep 04 12:52:25 UTC 2025
    - Last Modified: Sun Aug 31 08:19:00 UTC 2025
    - 16.4K bytes
    - Viewed (0)
  2. guava-gwt/pom.xml

                like to get an error. Currently we do, but if we add the extra <inherits> lines, we
                won't.
    
                I have one idea for a better approach, but it's painful, and I haven't tested it: We
                could postprocess Collect.gwt.xml to add <skip> lines for all the files that should be
                covered by testModule.gwt.xml. Maybe I'll try it someday.
    
    Registered: Fri Sep 05 12:43:10 UTC 2025
    - Last Modified: Thu Sep 04 21:35:58 UTC 2025
    - 19.4K bytes
    - Viewed (0)
  3. android/pom.xml

        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <!--
        Some tests need reflective access to the internals of these packages. It is only the
        tests themselves and not the code being tested that needs that access, though there's no
        obvious way to ensure that.
    
        We could consider arranging things so that only the tests we know need this would get
    Registered: Fri Sep 05 12:43:10 UTC 2025
    - Last Modified: Thu Sep 04 21:35:58 UTC 2025
    - 24.3K bytes
    - Viewed (0)
  4. pom.xml

        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <!--
        Some tests need reflective access to the internals of these packages. It is only the
        tests themselves and not the code being tested that needs that access, though there's no
        obvious way to ensure that.
    
        We could consider arranging things so that only the tests we know need this would get
    Registered: Fri Sep 05 12:43:10 UTC 2025
    - Last Modified: Thu Sep 04 21:35:58 UTC 2025
    - 23.9K bytes
    - Viewed (0)
Back to top