ENS testnet contract - bad jump when following quickstart tutorial

Question

Following the quickstart guidance using Ropsten testnet, I have done the following on a synced geth console:

> loadScript('/my/path/to/ensutils-testnet.js');
> new Date(testRegistrar.expiryTimes(web3.sha3('blipblop.test')).toNumber() * 1000)

<Date Thu, 01 Jan 1970 01:00:00 BST>

> ens.setResolver(namehash('blipblop.test'), publicResolver.address, {from: eth.accounts[0]});

"0x28f01d23b98a7b4fe1bc4324cb70e406714e1c14e64e632708f8ec44cebbde78"

When I look up the transaction on etherscan, it reports a bad jump destination and the name does no resolve:

> getAddr('blipblop.test')

"0x0000000000000000000000000000000000000000"

Am I doing something obviously wrong?

Should there be a delay between setting the resolver and being able to resolve the name?

Related (on main net): ENS setResolver bad jump destination

Answer 1

Here are the series of steps that worked (after jumping in chat with @atomh33ls).

> loadScript('/my/path/to/ensutils-testnet.js');

> testRegistrar.register(web3.sha3('blipblop'), eth.accounts[0],
                             {from: eth.accounts[0]});
// wait for block inclusion...

> ens.setResolver(namehash('blipblop.test'), publicResolver.address,
                             {from: eth.accounts[0]});

> publicResolver.setAddr(namehash('blipblop.test'), publicResolver.address,
                             {from: eth.accounts[0]});
// wait for block inclusion...

> getAddr('blipblop.test')
0x8058596db747ca76e2e769be88fb07cea5a47f89