Thanks Aaron, Sorry, did you notice clicking on the link provided “https://github.com/Acumatica/Test-SDK-Starter-Guide” results in a 404 page not found? Even searching Github for “Test-SDK-Starter-Guide” produces 0 results and searching for just “TestSDK” 1 result for Patrick Chan example. It is in a private repro? Does nothing then to help. My point about the “cannot file xxxxx.cs file has more to do with debugging my tests when using the TestSDK. I might of added some confusion, did ask about 3 or 4 separate issues. My main question is how to get my test working across all supported Acumatica versions we need to support. Seems next to impossible. Only after rolling back to an early build of of 2021 R2 (21.200.0145 -- very early build in 21 R2) was able to get my tests working. Updating to any build after that version they all fail. Would assume calling into the TestSDK as it is paired with each version of Acumatica, there shouldn’t be mismatched screen identifiers or if
Excellent answer that answered nothing… As for the logs, nope they aren’t showing up, all folders exists, no output is in them. Even better why not allow a custom logger, and optionally display in the console windows? From what is can tell you a generating html files? Sorry, might be nice for some, would really prefer all logs show up in one place, change the file names, most often just need the details i.e. “No such element findElement By.Xpath(“//eh”)”. I’ve read through most anything i could get my hands on, enough to have seen your comment Aaron about the ClassWrapper.exe breaking the web sites… There is nothing answering how to debug and get into the code...
Getting in and starting to use the TestSDK, running into a few issues. First question how we can debug into the code. Hit an error “Cannot locate xxxx.cs File”. Why is it failing? At best we only get some generic unactionable and unusable error message, where is the source so we can debug and see? Next, why are all the base, unmodified screens not provided as source within the TestSDK itself already? They had to be generated for creating the GeneratedWrappers.Accumatica anyway? The documentation for running the ClassGenerator.exe seems at best rather poor and incomplete. Examples for simple classes but what, why, and how to get pages with parameters? Doesn’t leave a lot of confidence this is ready for prime time to see even one of you own employees or community contributors mentioning a problem running the ClassGenerator.exe renders your website in a corrupted unusable state and allowed to ship. Leave a poor impression if this is the level of quality and testing going in
Sorry, think your suggestions were to do exactly what has been already done for cleaning up stuff? I’m seeing instances where:Acumatica does not show up in Windows Add/Remove program. Deleted all VDIRs in IIS and corresponding app pools. Delete the corresponding folder for the installed instance Remove the database Any folder under “Program Files” or x86Then run my install for the msiexcec to install the bootstrap setup to get ac.exe, to then run and then fails, a previous instance already exists… The question is more about where or how is it getting the information for previous instances. Where exactly is ac.exe once up and running reading the values to show, this is the information i’m really after which seems to be missed… Is it in a file, registry, some table in Sql’s master db?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.