gwpantazes

import io.github.bonigarcia.wdm.WebDriverManager;
import net.lightbody.bmp.BrowserMobProxy;
import net.lightbody.bmp.BrowserMobProxyServer;
import net.lightbody.bmp.client.ClientUtil;
import net.lightbody.bmp.core.har.Har;
import net.lightbody.bmp.proxy.CaptureType;
import org.openqa.selenium.Proxy;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.chrome.ChromeOptions;

gwpantazes

[22:18:20] [main/INFO] [LaunchWrapper]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker
[22:18:20] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLTweaker
[22:18:20] [main/INFO] [FML]: Forge Mod Loader version 14.23.5.2768 for Minecraft 1.12.2 loading
[22:18:20] [main/INFO] [FML]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_181, running on Windows 10:amd64:10.0, installed at C:\Program Files\Java\jre1.8.0_181
[22:18:20] [main/INFO] [FML]: Searching D:\users\George\Documents\Curse\Minecraft\Instances\StoneBlock\mods for mods
[22:18:20] [main/INFO] [FML]: Searching D:\users\George\Documents\Curse\Minecraft\Instances\StoneBlock\mods\1.12.2 for mods
[22:18:20] [main/WARN] [FML]: Found FMLCorePluginContainsFMLMod marker in Aroma1997Core-1.12.2-2.0.0.0.b161.jar. This is not recommended, @Mods should be in a separate jar from the coremod.
[22:18:20] [main/WARN] [FML]: The coremod aroma1997.core.coremod.CoreMod does not have a MC

gwpantazes

[19:20:47] [Server thread/WARN] [projecte]: Overwriting fixValueBeforeInherit for bigreactors:brore:0:0 to 0
[19:20:47] [Server thread/WARN] [projecte]: Overwriting fixValueBeforeInherit for bigreactors:dustmetals:0:0 to 0
[19:20:47] [Server thread/WARN] [projecte]: Overwriting fixValueBeforeInherit for bigreactors:dustmetals:3:0 to 0
[19:20:47] [Server thread/WARN] [projecte]: Overwriting fixValueBeforeInherit for actuallyadditions:item_dust:5:0 to 0
[19:20:47] [Server thread/WARN] [projecte]: Overwriting fixValueBeforeInherit for appliedenergistics2:material:46:0 to 0
[19:20:47] [Server thread/WARN] [projecte]: Overwriting fixValueBeforeInherit for appliedenergistics2:charged_quartz_ore:0:0 to 0
[19:20:47] [Server thread/WARN] [projecte]: Overwriting fixValueBeforeInherit for natura:materials:4:0 to 0
[19:20:47] [Server thread/INFO] [projecte]: Collected Mappings from moze_intel.projecte.emc.mappers.OreDictionaryMapper
[19:20:47] [Server thread/INFO] [projecte]: Collected Mappings from moze_intel.projecte.e

gwpantazes

georgep@georgepemaclap:~/Documents/workspace$ mongo
MongoDB shell version v4.0.2
connecting to: mongodb://127.0.0.1:27017
MongoDB server version: 4.0.2
Server has startup warnings:
2018-10-02T19:33:34.766-0500 I CONTROL  [initandlisten]
2018-10-02T19:33:34.766-0500 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2018-10-02T19:33:34.766-0500 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2018-10-02T19:33:34.766-0500 I CONTROL  [initandlisten]
---

gwpantazes

$ npm start
> [email protected] start /Users/georgep/Documents/GitHub/strapi-examples/hello-world
> node server.js

(node:3567) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
/Users/georgep/Documents/GitHub/strapi-examples/hello-world/node_modules/strapi-mongoose/node_modules/mongodb/lib/operations/mongo_client_ops.js:466
      throw err;
      ^

Error: Cannot find module 'mongoose'

gwpantazes

georgep:~/Documents/workspace/strapiDemo$ strapi install graphql
[2018-10-02T22:27:49.418Z] debug Installation in progress...
[2018-10-02T22:27:49.420Z] debug Installing the plugin from npm registry.
[2018-10-02T22:27:54.319Z] debug Plugin successfully installed from npm registry.
[2018-10-02T22:27:54.319Z] debug Moving the `node_modules/strapi-plugin-graphql` folder to the `./plugins` folder.
[2018-10-02T22:27:54.331Z] info The plugin has been successfully installed.
georgep:~/Documents/workspace/strapiDemo$ strapi start
(node:44092) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
(node:44092) UnhandledPromiseRejectionWarning: GraphQLError: Syntax Error: Expected Name, found }
    at syntaxError (/Users/georgep/Documents/workspace/strapiDemo/plugins/graphql/node_modules/graphql/error/syntaxError.js:24:10)

gwpantazes

$ npm install bleno

> [email protected] install /Users/georgep/node_modules/xpc-connection
> node-gyp rebuild

  CXX(target) Release/obj.target/binding/src/XpcConnection.o
../src/XpcConnection.cpp:143:89: error: too few arguments to function call,
      expected 2, have 1
  ...propertyValue = object->GetRealNamedProperty(propertyName->ToString());
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~                         ^

gwpantazes

#!/usr/bin/env python3

# How to use the Python pickle module to store arbitrary python data as a file.
# Cleaned up from the demo at: https://pythontips.com/2013/08/02/what-is-pickle-in-python/

import pickle

# Create something to store
a = ['test value','test value 2','test value 3']
# And something to compare against later

gwpantazes

#!/usr/bin/env python

import sys
import cv2
import subprocess
from subprocess import call


import aalib
import Image

gwpantazes

TestNG Annotation Precedence

This is an exploration of the precedence order for TestNG annotations so I can get a better understanding of which annotations come first.

As we can see in testOutput.log, there is a clear order to these methods (I wish they put that order more clearly in the TestNG Documentation...

The original question was "What is the difference between @BeforeMethod and @BeforeTest?" After seeing the results, it's clear that @BeforeMethod refers to each individual @Test annotated method, while @Test refers to the <test> organizational blocks in the testng.xml test suite file.

One thing that confused me is that @BeforeGroups and @AfterGroups both needed to be supplied with their groups, when I originally thought they would automatically run before all groups. It does make sense though, once I found out what was going on.