Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
Recently, I was watching a presentation in which JetBrains demonstrated a new, web-based code-browsing tool.
It's based on the IntelliJ code base, which supports code navigation operations such as show implementations, find usages, and so forth.
Unfortunately, I'm unable to find the presentation again. Does anyone know the name of this tool?
Since the tool is in pre-release, it wasn't possible to google any information about it. So thanks for any info!
It's called JetBrains Upsource and you can see it in action at https://upsource.jetbrains.com/
Upsource (that's the name of the tool) developer here. We just published a new preview build, by the way - check it out.
Regarding your browser compatibility question - I'm assuming you're getting an outdated browser warning, is it true? It shouldn't be the case with Firefox 20, though we generally support the last two released versions of every major browser (which, in case of Firefox, means 22 and 23). Upsource makes heavy use of latest web technologies to do what it does, therefore - no old browsers.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
For those that have used Karate robot for automating desktop applications in Windows written in Swing I'm curious to know what your experience was like? i.e. were the test runs reliable or flaky?
What was the best spy object tool you used to help identify Swing components and feed that to Karate scripts?
Also I see that https://github.com/intuit/karate/projects/3 MacOS support is in the backlog, is there any update on whether this update will support Swing apps on MacOS?
Appreciate your support, thanks.
Developer of Karate Robot here. Most known users are targeting Windows MFC / C++ / .NET or Delphi so there are no reports of Swing yet, but my guess is that it should work at least on Windows. "inspect.exe" works well to introspect the component tree. And we are looking for contributions for Mac, but there doesn't seem to be much interest - yet.
To summarize, I think your best bet is to contribute code to Karate, and you can make that decision based on your comfort with Java and your evaluation of how good Karate is in its current state and if it will "stay around", mature into a good desktop testing tool etc.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I am an IT also G suite Administrator.
When I use API explorer :　https://developers.google.com/admin-sdk/directory/reference/rest/v1/users/update
I got this error :
Error initializing the APIs Explorer
Cannot find specified method in converted discovery doc.
I check this page : https://developers.google.com/discovery/v1/reference/apis
But I still don't understand.
This seems to be a bug:
Try this API functionality is currently not working for some of the methods of Admin SDK, including the ones from Directory API and Reports API.
Instead of displaying the usual Try this API sidebar:
The message you mentioned is getting displayed:
Because of this, you cannot currently try these methods in the reference docs.
Issue Tracker:
This problem has already been reported before in Issue Tracker, and it has been forwarded internally by Google:
Error initializing the APIs Explorer
Anyone affected by this, please consider clicking the star on the top-left of the referenced issue in order to receive updates and to help prioritizing this.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am in the stage to find out what is Selenium. Its website looks very old. Here is a nodejs version of it.
I also found a good in browser testing solution protractor.
Are they designed to do the same thing? Which one should I use? Why Selenium website is so old, out of favor?
All tools you mention above like protractor, nightwatch are all based on selenium. If you are looking for a nodejs based solutions you can either directly use WebDriverJS (popularly known as selenium) or use many other frameworks which are developed on top of it. Every framework below offers unique features, you need to pick what works best for you. The basic advantage of using framworks is that they do most of the heavy lifting for you, that way your code is small and maintainable. UI testing is hard, the smaller the code you have the easier it is to maintain
protractor (good support if your app is angular)
nightwatch
nemo
webdriverio
wd
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I want to implement a Thunderbird-Addon and already found information on the mozilla web pages regarding Addon Development. However, some of the information is rather confusing, and thus I have some more specific questions:
1) Are Firefox Addon development and Thunderbird Addon development related? Some links may suggest so, others are indicated as "outdated"...
2) On the Mozilla web pages there are infos related to addons for Thunderbird 2,3, or 5. Isn't Thunderbird at version 31 currently? Probably I missed something here.
3) I want to extend the tagging mechanics in thunderbird, e.g. allowing relationships between tags, tag hierarchies etc. For that I would have to extend the existing data model. Can I do so?
4) Is there a good overview of the actual data model? Before I start programming something, I'd like to see which parts I have to touch and which I can leave alone.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Can anyone give advice, or point to any guides, on how to manage a community of open source software developers in writing api documentation?
A typical, unmanaged, starting point for most projects is to have a project wiki where anyone can freely create pages, add content to existing pages, edit existing content etc. The problem is that, despite people's best intentions, the wiki can easily end up being a disorganised, poorly written, incomplete, written in disparate voices etc etc.
So, what to do to improve the quality of the documentation?
I suspect a key ingredient is clear editorial/style guidelines, something similar to http://en.wikipedia.org/wiki/Wikipedia:Encyclopedic_style#Information_style_and_tone. Can anyone point to an example of such a guide tailored specifically to software apis?
Are there any other practices that people have found useful? E.g. form a core team of editors and accept that most documentation that gets added by the community will most likely need to be 'strongly edited'?
The short answer, that the solution is social/human and not technical. The way to get good documentation for any project is to have someone with time, in charge of doing high level organization for the documentation, and then being involved in the development and user communities to ensure that the documentation remains up to date and continues to address the problems and confusions that users typically have.
Community projects have accepted that you need point people (i.e. "managers," for aspects of the project like "translation," and "release," and for various components. The same thing needs to happen for documentation.
As for tools, Sphinx is really great though it's not "wiki like," exactly you can use whatever version control system your project is comfortable with to store documentation and configure your web server to rebuild the documentation following commits/updates/pushes. Which has always worked just fine for any project I've worked on/with.